Personally I’ve decided that the next version of Terminator is just going to use meson and ninja for installation. It plays nicely with the system python, and all of the actual packaging tools out there (dpkg, pkg, rpm, etc) and doesn’t require constant maintenance once set up. Python packaging tools are all terrible, and are far too interested in use-cases I don’t care about. don’t @ me.
I just want a standard library solution to replace Poetry and Pyenv. I’ve hit two of the three issues in the article (and many more not listed), but I still use Poetry because it solves the problem. Switching to another non-standard library solution means all my teams now need to learn whatever gotchas those projects have, as well.
I hope that uv could eventually become that. It’s for the most part standards based or adds minor changes on top that could eventually become standards.
As I understand it, much of the frustration from the Linux-distro side over adoption of Rust into Python tools is over platform support: what do you do if your distro supports a platform Rust doesn’t? This feels especially nasty for a distro like Gentoo which is designed entirely around compiling from source on the target machine.
I don’t personally pay that much attention. I just know platform support was the cited reason for a lot of the anger when the Python cryptography package rewrote its compiled extension in Rust.
Personally I’ve decided that the next version of Terminator is just going to use meson and ninja for installation. It plays nicely with the system python, and all of the actual packaging tools out there (dpkg, pkg, rpm, etc) and doesn’t require constant maintenance once set up. Python packaging tools are all terrible, and are far too interested in use-cases I don’t care about. don’t @ me.
I just want a standard library solution to replace Poetry and Pyenv. I’ve hit two of the three issues in the article (and many more not listed), but I still use Poetry because it solves the problem. Switching to another non-standard library solution means all my teams now need to learn whatever gotchas those projects have, as well.
I hope that uv could eventually become that. It’s for the most part standards based or adds minor changes on top that could eventually become standards.
I asked the author about uv on Mastodon, he doesn’t look enthusiastic https://piaille.fr/@mgorny@treehouse.systems/113686941213187687 I’m a bit surprised by his response, though.
As I understand it, much of the frustration from the Linux-distro side over adoption of Rust into Python tools is over platform support: what do you do if your distro supports a platform Rust doesn’t? This feels especially nasty for a distro like Gentoo which is designed entirely around compiling from source on the target machine.
Rust is ported to all Gentoo platforms except for alpha and hppa.
there you go
I don’t personally pay that much attention. I just know platform support was the cited reason for a lot of the anger when the Python
cryptographypackage rewrote its compiled extension in Rust.PyPA delenda est.
Yes, it has been very clear for many years that there should be one way to do it. UV is promising. I hope it can become a standard tool.