31–40 of 64 posts
EW. Avoid. For the tenth time in these comments, use poetry. It's a real shame PyPA endorsed this to be honest, I hope that can be reversed at some point in the future.
Well, except one thing: If I do `poetry update `, it starts upgrading other packages as well. I'm not sure what that's about...
Earlier quoted context omitted.
Isn’t this what pip freeze is for?
pip freeze only pins the version of direct, not transitive dependencies. Meaning you don't get deterministic builds.
Gonna take a look at poetry, but would love to hear what problems people have had with pipenv?
What does this tool provide over an in-project .venv/ directory created by venv and populated by pip from an etc/pip/requirement.txt file containing all the packages by version? There seems to be a lot of activity in this area for a seemingly solved problem. Having solved it, people appear to wish to expand the problem to something bigger (such as multiple interpreter versions, for example) I believe the most-common…
It is a solved problem for other languages. Pip has soooo many issues. The biggest IMO is pip doesn't provide a way to pin indirect dependencies, so there is no good way to ensure that other people working on a project are also using the same dependency versions. You can do it with extra tooling of course - and that's what poetry and pipenv do.
Earlier quoted context omitted.
pip freeze only pins the version of direct, not transitive dependencies. Meaning you don't get deterministic builds.
What do you mean? If you run pip freeze inside a venv it will print every user-installed module and their dependencies. When installing them in a new venv as a requirements file, you end up with the exact same set of modules.
There wasn't a full release for a year and it broke my pip on Ubuntu 18.04 as I recall - literally it stopped pip from working after I installed it (can't remember why). Avoid.
What does this tool provide over an in-project .venv/ directory created by venv and populated by pip from an etc/pip/requirement.txt file containing all the packages by version? There seems to be a lot of activity in this area for a seemingly solved problem. Having solved it, people appear to wish to expand the problem to something bigger (such as multiple interpreter versions, for example) I believe the most-common…
It is a solved problem for other languages. Pip has soooo many issues. The biggest IMO is pip doesn't provide a way to pin indirect dependencies, so there is no good way to ensure that other people working on a project are also using the same dependency versions. You can do it with extra tooling of course - and that's what poetry and pipenv do.
EW. Avoid. For the tenth time in these comments, use poetry. It's a real shame PyPA endorsed this to be honest, I hope that can be reversed at some point in the future.
Poetry is basically perfect, it does what it says and has no surprises. Well, except one thing: If I do `poetry update `, it starts upgrading other packages as well. I'm not sure what that's about...