3 ms·
Valid, but you can make three binaries that will work for the most common use cases. (I've done this) For a project as big as this, doing so is trivial, vice of
by the__alchemist 2y ago
Valid, but you can make three binaries that will work for the most common use cases. (I've done this) For a project as big as this, doing so is trivial, vice offloading it onto the users.
- nine_k 2y ago> offloading it onto the users Not end users but distro maintainers. If you run almost any Linux distro imaginable, it has Python already in the distro. If you want to try a version that's not yet even supported by the unstable branch of your distro, or not available on some PPA, etc, you need to be well enough versed in its dependencies to build it yourself. Alpha-quality software, of course, benefits from more eyes, but it mostly needs certain kinds of eyes.
- Joeboy 2y agoI haven't really used it in anger, but I believe `uv` can install pre-compiled python binaries (from... somewhere?). Maybe also pyenv?
- scottyeager 2y agoWith pyenv it's built from source. That's pretty seamless if you have the build dependencies installed. With rye and uv you get the prebuilt portable versions from indygreg. Those have some significant deviations from what you get with a system package or pyenv built version, so there can be some caveats.