4 ms·
uv handles most, if not all, of those cases. > - else does it have a pyproject.toml? if so poetry install and then prefix all commands with poetry run That's
by kortex 1y ago
uv handles most, if not all, of those cases.
> - else does it have a pyproject.toml? if so poetry install and then prefix all commands with poetry run
That's not even correct. Not all projects with pyproject.toml use poetry (but poetry will handle everything with a pyproject.toml)
Just try uv first. `uv pip install .` should work in a large majority of cases.
pipenv is on the way out. bare `setup.py` is on the way out. `pyproject.toml` is the present and future, and the nice thing about it is it is self-describing in the tooling used to package.
- marifjeren 1y ago> That's not even correct. Not all projects with pyproject.toml use poetry I didn't say "all projects with pyproject.toml use poetry"
- eyegor 1y agoI wish setup.py was actually on the way out, but sadly, it's the only straightforward way to handle packages that use cython or interop. In these cases, libraries use setup.py to compile the dll/so/dylib at install time. Naturally this is a bit of nightmare fuel since installing gets arbitrary code execution privileges but there's no real standard for privileges in python package installs.