Re:Rye and Uv: August Is Harvest Season for Python Packaging
by globular-toast on Thursday August 22, 2024 @02:26AM
(#41317379)
What you mean by "project" is a service. A service includes the Python interpreter. Choosing and provisioning the interpreter seems out of scope for pip or any other Python-specific tooling IMO. What if your service needs another interpreter like Ruby, or a database, message broker etc? Your Python tool won't help with that. This is what docker, and higher-level orchestrators like docker compose and kubernetes, and pyinstaller are for.
[ Parent
| on HN ]
Re:Rye and Uv: August Is Harvest Season for Python Packaging
by wodenokoto on Thursday August 22, 2024 @07:30AM
(#41319048)
> Choosing and provisioning the interpreter seems out of scope for pip or any other Python-specific tooling IMO.
It's in-scope for Rye and hatch.
And I agree with that choice. Choosing a python version is as integral a dependency as choosing a version of numpy.
Re:Rye and Uv: August Is Harvest Season for Python Packaging
by globular-toast on Thursday August 22, 2024 @09:33AM
(#41320092)
Sure, but you can only document that choice in your pyproject.toml, which is well-established. You have no idea how someone is going to provide that interpreter. You don't know what OS or how to provision an interpreter. If you are the person provisioning that interpreter then just use the tools you already know, not yet another tool to do basic stuff like install an interpreter.