PEP 684: "A Per-Interpreter GIL" has been accepted for Python 3.12!
https://discuss.python.org/t/pep-684-a-per-interpreter-gil/19583/42?u=hugovk
Seems like you can add a configuration with the command line, which I don't know how to use, and which doesn't add a UI toggle.
Has anyone out there gotten Wireguard working with the NetworkManager UI?
Seems like there used to be [a plugin](https://mox.sh/sysadmin/wireguard-networkmanager-gnome/) that added Wireguard endpoints as VPNs, but it got upstream support and NetworkManager now can import Wireguard configurations and.... doesn't show them in the UI. The plugin doesn't work anymore.
@pganssle @jerub How about EDTF (level 0) by the Library of Congress? https://www.loc.gov/standards/datetime/
@jerub Which I find mildly annoying, since the discussion always goes, "We should document that we accept ISO8601!"
"Ok, but that's a ton of work because of XYZ, and includes formats that, if you encounter them, are more likely to be typos than deliberate choices."
"Err, ok, let's do RFC3339."
"Ok, so datetime only and time zone is required, as is the T separator."
"Well no that's too strict, I guess we should just accept some ad hoc defined formats that are ISO8601-like."
@jerub RFC 3339 is stricter than the subset of ISO 8601 that most people talk about, because it is only a datetime format and *requires* a time zone.
As far as I can tell there is no standard that describes the subset of ISO8601 that people actually care about.
Did you know that ISO 8601 is a very large standard that describes more than a single date and time format?
It describes periods, repetitions, many different syntax of describing years, week-of-year, day-of-year, seasons, quarters, semesters, trimesters.
It's mostly unknown because the standards are paywalled: you can't just read ISO 8601 without paying ISO money.
Most of the time, when people refer to ISO 8601, they mean the subset that is described in RFC 3339.
Hey, remember that podcast I announced last year? https://www.conferencetalk.am/episodes/0002/assembling-an-organizing-team/
This looks like a fun RSE job on Colorado:
@pganssle Two Lebanese television channels and an airline are sticking with the old rules...
https://edition.cnn.com/2023/03/25/middleeast/lebanon-daylight-savings-intl/index.html
And as usual, if you have the ear of someone involved in setting time zone policy in Lebanon (or anywhere), maybe send them this article: https://codeofmatt.com/on-the-timing-of-time-zone-changes/
Latest version of tzdata (2023b) is out (on PyPI and upstream!): https://pypi.org/project/tzdata/
This includes a change to Lebanon's Daylight Saving Time going into effect... this weekend, so don't delay in your updates if you work with any datetimes in Lebanon!
If you are a #git expert and understand how `cherry-pick` works at a fundamental level, I'd appreciate if you could take a look at this StackOverflow question: https://stackoverflow.com/q/75825183/467366
Trying to figure out the best way to merge a specific PR that will make importing `datetime` significantly faster.
There actually does seem to be quite a bit of overlap between what he's talking about and what @simon has done with datasette and dogsheep.
Found it: this was Pascal van Kooten on Podcast.\__init__: https://www.pythonpodcast.com/nostalgia-personal-data-repository-episode-248/
He was talking about his project Nostalgia: https://nostalgia-dev.github.io
Aww yeah, I am very ready for some lab grown meat: https://www.npr.org/sections/health-shots/2023/03/21/1165071880/fda-gives-2nd-safety-nod-to-cultivated-meat-produced-without-slaughtering-animal
I'm guessing just 2-4 more years of bureaucratic hurdles until it's available but expensive, then 15 more years until I can eat a cultivated eagle steak with elephant marbling.
Programmer working at Google. Python core developer and general FOSS contributor. I also post some parenting content.