Paul Ganssle @pganssle@qoto.org
Programmer working at Google. Python core developer and general FOSS contributor. I also post some parenting content.
Joined Nov 2019
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
@brettcannon Is that in addition to a group policy through work?
Not that it doesn’t seem like a reasonable amount of insurance (particularly with no kids), just curious.
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.
@LouisIngenthron That's not a real solution to the problem for any number of reasons which should be obvious.
Also, I've been able to meet these requirements (and more!) since 2008. It's tragic the direction computing has taken ☹
@LouisIngenthron Very good camera and an SDHC expansion slot. Strong preference for an unlockable bootloader because I've never had a non-rooted phone and I think being unable to root it would put a crimp in my workflow.
Last year I decided that I was willing to compromise the SDHC expansion slot requirement (☹) if I could get 1TB of space, but after a year I have not been able to find a Samsung Galaxy S22 Ultra 1TB with an Exynos chipset (the only kind you can root).
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.
I can’t believe I’ve been trying to find a new phone that meets my requirements for a year and I still can’t find one. ☹
Paul Ganssle
boosted
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 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.
Paul Ganssle
boosted
@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.
Paul Ganssle
boosted
@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.”
Paul Ganssle
boosted
@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.
Paul Ganssle
boosted
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.
Programmer working at Google. Python core developer and general FOSS contributor. I also post some parenting content.
Joined Nov 2019
