FYI, If you don't already follow @brainwane, you probably should. From what I can tell, she's a thoughtful person in every aspect of her life, including curating an excellent feed of diverse, high quality content (both what she writes and what she boosts).
Also, if you have the opportunity to be her friend, take it, because she's a wonderful person.
Hola Fediverso 🐍
nos vemos en Tenerife el 6, 7 y 8 de octubre #PyConES23
This Thursday I'll be giving a preview of my PyCon talk at the Boston Python meetup. If you are in the Boston area, come on down! https://meetu.ps/e/LZhX0/1z7D4/i
Curious to know if anyone is willing to share — particularly those with kids and a large disparity between your income and your spouse's — how much life insurance do y'all have?
Right now I have a $1M 30 year policy (plus some coverage and stuff through work that probably adds up to another $1M or so in value for my heirs), but I'm starting to feel like this is way too little.
My Pebble is on its last legs, too. I had to give it open-case surgery last week (new battery), but that just bought me some time.
All of this is really affecting my inner techno-optimist.
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/
Programmer working at Google. Python core developer and general FOSS contributor. I also post some parenting content.