Post #3931110

2026-07-19 01:18 UTC

@delilah@derg.social Objectively false, just encountered it with stuff (with little or no external dependencies) written with 3.12 failing to run on 3.13, and stuff written with 3.13 failing to run on 3.14 (and stuff written right when 3.14 came out failing to run on 3.14.5/3.14.6, but maybe that was just a third-party library being terrible or something)

Replies (1)

@senil@gts.social.senil.me 2026-07-19 09:28

@nytpu@tilde.zone @delilah@derg.social Literally was having this exact issue when I was poking around with morshutalk. Every library it used makes assumptions that only worked for that version of Python, or relied on existing functionality in those versions of Python that since got completely removed for... reasons. Which is largely why if I do end up recreating it, it's not going to be with Python (idk what with if i do, later problem). Their versioning is a confusing mess and in order to be up to date with non-EOL versions you have to routinely accept that there'll be breaking changes in your libraries and code now and then, which is really frustrating IMO. Especially since new versions happen every year & you get support for one version for five years on the dot. Have fun porting older projects every couple of years! Hope those libraries you used still work! Oh, they haven't been updated in two years? lol don't use the major releases, fuck you.

Open ##3931109