News for hackers. Stuff that matters.
Re:Ask HN: Whose building on Python NoGIL? by throwaway127482 on Saturday December 21, 2024 @07:45PM (#42483562)
What have they broken on 3.x? Genuine question as I haven't followed python's development super closely
Re:Ask HN: Whose building on Python NoGIL? by skeledrew on Saturday December 21, 2024 @09:43PM (#42484041)
Some seldom used standard modules have been deprecated and later removed. Like recently I revisited a project I initially made using v3.6, but it broke on v3.13 due to an indirect dependency no longer present in the stdlib. It was a simple fix though as a quick search identified the issue and pointed to the removed module in a package on PyPI.
Re:Ask HN: Whose building on Python NoGIL? by hamandcheese on Sunday December 22, 2024 @01:52AM (#42484803)
Yeah, it's nothing crazy, but it makes upgrades a lot more unpredictable. It's harder to communicate to management why the 3.x update took a day and the 3.y upgrade took a whole quarter.

It's harder to upgrade services in a central way with any amount of leverage, and generally requires more coordination overhead, and moving more carefully.

Compare with, say, golang, where it's pretty much a non-issue. My experience with Ruby was a lot better too, until Ruby 3, but hey, that was a major version bump!

Re:Ask HN: Whose building on Python NoGIL? by fulafel on Sunday December 22, 2024 @02:33AM (#42484918)
Python 3.6 is from 2016 and 3.13 is from 2024. Similar things happen on most platforms on this timescale, eg on the Java side[1], you'd be going from Java 8 to Java 23.

Clojure is pretty good even on that timescale though.

[1] See eg https://stackoverflow.com/a/50445603 up until 2021

Re:Ask HN: Whose building on Python NoGIL? by skeledrew on Sunday December 22, 2024 @12:56PM (#42487946)
Yep it's totally understandable, and OK by me as these changes are documented in the release docs and the fix a pip install away.
Re:Ask HN: Whose building on Python NoGIL? by trallnag on Monday December 23, 2024 @04:53AM (#42493191)
I often see people recommending Python as a replacement for Bash scripts (utilizing common Unix tools like grep and awk). I'm pretty sure a script from 2016 will still be working fine now.
Re:Ask HN: Whose building on Python NoGIL? by swiftcoder on Monday December 23, 2024 @05:03AM (#42493241)
> I'm pretty sure a bash script from 2016 will still be working fine now.

In some environments, yes. A bunch of platforms have started using bash-compatible (but not actually bash) shells like fish to help with startup performance. Apple has upgraded from a truly ancient version of bash to a somewhat-modern one in that time (and then gone all-in on zsh instead). Things change on the scale of a decade.

Re:Ask HN: Whose building on Python NoGIL? by jkaplowitz on Tuesday December 24, 2024 @12:12PM (#42503214)
And yet, if the script is written to POSIX sh standards and has the #!/bin/sh shebang line, none of that breaks.

Yes, of course, things do change incompatibly in a decade, probably including some of the nonstandard platform-specific commands called by the script regardless of which dialect of shell. But people who use a nonstandard shell dialect - however common it might be at the time of writing - should be prepared for that shell to become uncommon, absent by default, installed at a different path, incompatibly changed, or otherwise unusable a decade later to an extent that people writing to the standard do not.

Re:Ask HN: Whose building on Python NoGIL? by nuancebydefault on Monday December 23, 2024 @10:14AM (#42494954)
The bash side will still work but the tools called by bash won't. Same goes for python/packages.
Re:Ask HN: Whose building on Python NoGIL? by Too on Tuesday December 24, 2024 @02:07AM (#42500189)
Assuming the script even worked fine in the first place. Usually quite unlikely.
Re:Ask HN: Whose building on Python NoGIL? by fulafel on Wednesday December 25, 2024 @02:55AM (#42507579)
They break more often than Python scripts, from reasons unrelated to bash versions, though.
Re:Ask HN: Whose building on Python NoGIL? by SOLAR_FIELDS on Sunday December 22, 2024 @12:18PM (#42487701)
Removal of setuptools in 3.12 broke a ton of legacy builds. Basically created a wall of forced package upgrades for a huge amount of packages in PypI where end users have to bump a bunch of stuff if they want to migrate from < 3.12 to 3.12+
Re:Ask HN: Whose building on Python NoGIL? by Flimm on Sunday December 22, 2024 @04:06PM (#42489101)
setuptools was never part of Python's standard library. I think you're thinking of distutils which was removed from Python in the 3.12 release. You can easily access distutils again by installing a package from PyPI.
Re:Ask HN: Whose building on Python NoGIL? by SOLAR_FIELDS on Sunday December 22, 2024 @11:33PM (#42491812)
You are right, it was distutils. Good call out. Not sure why I thought of setuptools.
Re:Ask HN: Whose building on Python NoGIL? by JamesonNetworks on Monday December 23, 2024 @06:41AM (#42493700)
This comment thread is a microcosm of the problems with python packaging :D I appreciate the work the ecosystem does on it and everyone is doing their best, but its still a hard problem that doesn't feel solved
Re:Ask HN: Whose building on Python NoGIL? by feznyng on Wednesday December 25, 2024 @12:43PM (#42509949)
Check out uv if you haven’t.
Re:Ask HN: Whose building on Python NoGIL? by CamouflagedKiwi on Monday December 23, 2024 @05:33AM (#42493383)
One that I ran into at previous job: 3.10 removes the ability to implicit cast floats to ints in a bunch of places. That was very much a breaking change for a bunch of code out there.
Re:Ask HN: Whose building on Python NoGIL? by pletnes on Monday December 23, 2024 @09:04AM (#42494434)
Never heard of. Do you have any concrete examples? Would be good to know about for me in 2025.
Re:Ask HN: Whose building on Python NoGIL? by brianwawok on Tuesday December 24, 2024 @07:11PM (#42505923)
Comparing ints and floats sounds like a pretty high nono in basically any language ever. Why more python projects should use MyPy and not freely switch float to int to decimal. They aren’t the same thing.
Re:Ask HN: Whose building on Python NoGIL? by Kwpolska on Monday December 23, 2024 @07:38AM (#42493977)
They have been removing features every release for the past few years. Code that was working fine on 3.10 may break on 3.13 just because it was using a feature they didn't like.
Re:Ask HN: Whose building on Python NoGIL? by formerly_proven on Monday December 23, 2024 @08:53AM (#42494372)
Every release removes / breaks stuff in the standard library and has been for a while. That's because prior to ~3.2 or so, deprecations were basically never followed up on, but now deprecation means it's going to be removed.

E.g. Python 3.12 has deprecated datetime.utcnow(). So it will probably be removed in Python 3.14 or 3.15.

For all intents and purposes, "Python 3" is now the brand and "Python 3.x" releases are major, breaking releases.

Re:Ask HN: Whose building on Python NoGIL? by physicsguy on Tuesday December 24, 2024 @03:29AM (#42500522)
The async initial implementation changed in such a way as to break existing code