I am unreasonably pleased that #PyBay has open wifi with no captive portal.
@pamelafox I pretty only write pytest tests in classes when I might subclass them for some reason (or when directly migrating something based on unittest), but using them as a namespace makes a certain amount of sense.
So this happened at TSA today, which means it's time to get new headphones. Are bone conduction headphones still the best option for headphones that you can wear all the time but you can hear it when people talk to you?
My ideal headset would be very discreet, such that people can barely tell you are wearing them (or if they are visible I would prefer if people felt comfortable talking to me while wearing them).
I do not use Apple products.
@nowis To be fair, how could someone know more than one language? What are these people, computers?
@ccriss92 No te preocupes, ahora es temporada de ascensos, y cuando asciendan a la gente que hizo esta barbaridad, se puede arreglarla para que la siguiente tanda de empleados pueda conseguir sus ascensos. Es el círculo de los ascensos.♻️
@andrewblasco @jordibal @ccriss92 @Paroxia Si usas NewPipe, puedes ir a Ajustes > Video y Audio > Prefiero audio original.
Give this a go to help guide the future of the web!
Though I will admit that there are also NO OTHER REASONS for putting lazy imports in a context manager. It's just the backwards compatibility use case and no others.
I further contend that other than `contextlib.suppress`, there is no other situation where lazy imports in a context manager could be dangerous.
*Ahem* I hereby affirmatively state that the ONLY ergonomic way to functionally backport lazy imports would be to use a context manager. Even a *genius* could not come up with a better way.
I think I should have used Cunningham's law instead of asking questions in [this post](https://discuss.python.org/t/pep-810-explicit-lazy-imports/104131/176). I suspect I would have gotten more people weighing in.
Let me post a *non*-subtoot for once... We made a thing!
https://discuss.python.org/t/pep-810-explicit-lazy-imports/104131
@sethmlarson @adamchainz So probably 25% chance it is still using six in 2030 😛
@sethmlarson @adamchainz I just need to write the documentation on issue #1130 to merge it, I think. Probably like 2 or 3 days' work to do the whole migration, so if in the next 5 years I have 2 or 3 uninterrupted days and I don't have to spend them fighting bitrot on the CI, dateutil should drop six before then.
Programmer working at Google. Python core developer and general FOSS contributor. I also post some parenting content.