4 ms·
Everytime you install a package through poetry, you're also running pip code. You didn't even understand the point they made: the need for Pipenv and poetry wo
by 411111111111111 4y ago
Everytime you install a package through poetry, you're also running pip code.
You didn't even understand the point they made: the need for Pipenv and poetry would pretty much go away if pip added support for a proper lockfile and venvs. And that's the only correct choices as pip is already pythons package manager.
- bombolo 4y agoWhat's the problem with first doing the venv thing and then running pip?
- numbsafari 4y agoAny multi step process is guaranteed to produce random assortments of workflow tools to manage those steps which will seek to replace the original process as the one true process. If there two steps, one part of the community will insist they belong in: a makefile, bash script, python script, lambda network service, bazel, pants, scons, terraform, ansible, npm …
- bombolo 4y agoSo we should have 1 single shell command to do literally everything?
- 411111111111111 4y agobefore poetry and pipenv was a thing, pretty much everyone was recommending the virtualenvwrapper script instead of using venv directly... so yes, thats what it ultimetaly always ends up as.
- bombolo 4y agoOne might invest 20 seconds to learn how to use it, but to each their own :)
- numbsafari 4y agoNot what I would or wouldn’t do personally, but what happens generally in practice.