3 ms·
FWIW, I placed my early bet on pipenv, but it had some significant bugs and development had stagnated (seems like it might be picking up again). When we decide
by rsyring 5y ago
FWIW, I placed my early bet on pipenv, but it had some significant bugs and development had stagnated (seems like it might be picking up again).
When we decided to move away, I looked at Poetry and pip-tools. Poetry seemed too different to me, don't remember specifics, but felt like too much would need to change. All I wanted was the ability to lock package versions.
Enter pip-tools. It was really simple, felt familiar, and just worked. So, that's what we chose and it's what we use to this day.
- tedmiston 5y agoNot sure what you saw but Poetry works as simply as you described. Just `poetry init`, `poetry add foo`, `poetry shell` or `poetry run ...`, etc. I use it every day.
- lmns 5y agoI'm surprised that pip-tools isn't more popular. For the stuff I do with Python (small CLI tools, casual webdev) it's completely adequate. I can pin down my dependencies, upgrade to a new pinned state and sync my venvs with the packages specified in the generated requirements.txt. Maybe there are more elegant or modern ways of doing this, but for my personal projects I haven't found a reason to switch to anything else. Btw, there is also micropipenv[0] now which can consume both poetry and pipenv lockfiles and convert them to pinned down requirements.txts as generated by pip-tools. [0] https://pypi.org/project/micropipenv/ https://pypi.org/project/micropipenv/