Petr Viktorin

Public Key

npub16d3vzzctq3d59krau5kmfesuzgmdalh8627warl8cct0khyml7usv54r20

NIP-05 Address

Profile Code

nprofile1qqsdxckppv9sgk6zmp772td5ucwpydk7lmna908w3lnuv9hmtjdllwgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsss6huz

Publishing to

offchain.pub

relay.damus.io

nos.lol

Author Public Key

npub16d3vzzctq3d59krau5kmfesuzgmdalh8627warl8cct0khyml7usv54r20

Show more details

Last Notes

2025-06-27 10:31:58 UTC

- reply

Asking as a complete outsider: could insulation be a factor here? It's a bit hard to tell but some of the photos seem to show bare wires, for which grooves in the hard-to-reach side would make sense.

2024-12-21 04:20:00 UTC

- reply

Partially. AFAIK, much of the scientific ecosystem drops Python support after 3 years, not 5: https://scientific-python.org/specs/spec-0000/
I don't know who your clients are. But I imagine that if we do add `sys.supported_until`, you'll see someone show up with an enterprise distro, running Python 3.6 with a 2030 EOL date baked into it. (And it would be correct because they do get backports for critical security fixes, and the system's built to get those fixes actually installed.)

2024-12-20 18:54:49 UTC

- reply

In CPython's case, "support" means "we'll release new versions with non-breaking bugfixes".
If they don't update every few months, what good is this support for?

2024-12-20 13:36:14 UTC

- reply

That's EOL for source releases from python.org. If you get the binary installers, or Conda builds, python-build-standalone, or a distro package, you'll get different dates -- and also different *kinds* of support.
IMO, the devguide chart is aimed at core devs, to see when to backport what.
Perhaps we need user-facing docs... but then we'd probably need to define what we promise as “support”.

2024-12-20 08:13:20 UTC

- reply

What kind of support? I don't think this can be reduced to a single date.
If you build your own fork, would you need to fill this in?