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
@trinsec Seems like it,
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 Yeah, something you can implement that is not suitable for most peoples' use cases 😛 The `T` is not really the big issue with RFC3339.
@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.
@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/
@glyph Unfortunately no one right now (Fedi or Twitter) has a good system for plugins to allow you did reorder or filter your own feeds (other than implementing your own client, which is way overkill and requires multi-platform support), or I'd be training a classifier to remove even vagueposting. One day, maybe...
@glyph I mean if you include #usnews or #news or something, it would allow me to filter it out automatically.
I'm not bothered by the fact that it's vague, I'm bothered by the fact that the vagueness prevents be from filtering it out, which imposes upon me the knowledge that something unpleasant is in the news.
@glyph TBH I'm not crazy about these oblique references. I don't know if you are worried about summoning Reply Guys or something, but I've got filters set up so that it is increasingly rare that I have news, drama or politics in my feed, but stuff like these oblique references manage to get through.
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
@hugovk Yep, chaos is pretty inevitable with a change on this short notice, though Lebanon is a particularly egregious example of this now.
Programmer working at Google. Python core developer and general FOSS contributor. I also post some parenting content.