Paul Ganssle @pganssle@qoto.org

@glyph Solid legal advice: "It's not copyright infringement if you copy it from a parallel universe."

#pyconus #PyConUS2023

@glyph "If you learn anything from this talk, it should be, 'Use the keyring module'"

Too late! I already learned a different thing!

#pyconus #PyConUS2023

My takeaway from @glyph's talk: give all your passwords to a CLI tool you installed from PyPI to help you memorize them: 😉

https://github.com/glyph/pinpal

#pyconus #PyConUS2023

@brianokken Have you seen this? https://github.com/abid-mujtaba/new-fixtures

#pyconUS #PyConUS2023

I like how @hynek's example of an exception to the no subclassing rule of thumb is... exceptions.

#pyconus #PyConUS2023

@hynek Protocol: "brand new" feature from Python 3.8.

(These are great by the way: https://blog.glyph.im/2020/07/new-duck.html)

Pop quiz from @hynek: which one is called?

#pyconus #PyConUS2023

It went by pretty quick, so you may have missed it, but I think there's a good lesson to take from James' humility about his own design judgement.

I think I have good design judgement, but I am constantly recognizing designs in the wild that are wildly successful that don't commonly exhibit the failure modes I would have predicted.

#pyconUS #pyconUS2023

t's actually a good strategy for giving examples of APIs that can be improved that I've used in the past: use your own code for negative examples 🙂

Love James Powell wearing his NumFocus sweatshirt while putting scipy's interface on blast 😅😉 #pyconus #PyConUS2023

@nedbat Is there a place people are leaving their juggling stuff? I don't really want to carry mine around all day 😅

Anyone know the person who did the lightning talk about public records / genealogy? I didn't catch his name.

#pycon #pyconus #PyConUS2023