3 ms·
In Python's case, as the article describes quite clearly, the issue is that the design of "working software" (particularly setup.py) was bad to the point of ins
by pxc 10mo ago
In Python's case, as the article describes quite clearly, the issue is that the design of "working software" (particularly setup.py) was bad to the point of insane (in much the same way as the NPM characteristics that enabled the recent Shai Hulud supply chain attacks, but even worse). At some point, compatibility with insanity has got to go.
Helpfully, though, uv retains compatibility with newer (but still well-established) standards in the Python community that don't share this insanity!
- s_ting765 10mo agoMy gripe is with Rust rewrites. Not uv. Though I very much think uv is overhyped.
- eduction 10mo agoActually uv retains compatibility with the setup.py “insanity,” according to the article: > uv parses TOML and wheel metadata natively, only spawning Python when it hits a setup.py-only package that has no other option The article implies that pip also prefers toml and wheel metadata, but has to shell out to parse those, unlike uv.
- pxc 10mo agoUgh. Thank you for the correction. :(
- eduction 10mo agoI mean, you’re on the right track in that they did cut out other insanity. But unclear how much of the speed up is necessarily tied to breaking backward compat (are there a lot of “.egg” files in the wild?)
- zahlman 10mo ago> (are there a lot of “.egg” files in the wild?) Not as far as I can tell, except perhaps in extended-support legacy environments (for example, ActiveState is still maintaining a Python 2.x distribution).