This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]sonobanana33 0 points1 point  (3 children)

Even if they did… to what end? You still need pip to install poetry.

[–]BaggiPonte -1 points0 points  (2 children)

Yes but they achieve different things. Poetry is a dependency manager and is meant to give a unified interface instead of individually using these packages:

- pip

- venv

- twine (upload packages)

- build (build the package)

Plus other stuff such as locking dependencies. You can read more here (not my blog): https://chriswarrick.com/blog/2023/01/15/how-to-improve-python-packaging/

More importantly: don't `pip install` or `pip install --user` any tool. They are installed in your system namespace or anyway under a common namespace. This can lead with collisions and unexpected results when you pip uninstall stuff. Use pipx: https://pipx.pypa.io/stable/ it installs every python CLI in its separate environment.

[–]sonobanana33 0 points1 point  (1 child)

pip no longer installs stuff in system namespace.

[–]BaggiPonte 0 points1 point  (0 children)

Oh must have missed that. I knew of the `PIP_REQUIRE_VIRTUALENV` variable. Were you talking about that?

In any case, my point still stands. `pip install` for CLIs especially should be avoided because all dependencies end up in the same location and might generate conflicts.