3 ms·
Just use poetry[1], there isn’t any reason not to. You can create and manage virtualenvs by hand if you’d like, but why do that to yourself? 1. https://python-
by orf 5y ago
Just use poetry[1], there isn’t any reason not to. You can create and manage virtualenvs by hand if you’d like, but why do that to yourself?
1. https://python-poetry.org/ https://python-poetry.org/
- fmakunbound 5y agoI sure want to believe this is the last tooling I’ll need to use for Python tooling nirvana, but that’s what they told me about pip, pip3, venv, vitrualenv, conda.. And one coworker just suggested I just run the script in Docker. Ugh
- orf 5y agoI’m not sure anyone said pip or virtualenv where the end of the road for Python tooling nirvana. They are just building blocks, poetry (or other tools) stick them together. That being said, I’ve been using Python for 16 years now and for me poetry is pretty close to nirvana. Not perfect, but really good. Handles virtualenv management, locking, dependency specification, etc etc.
- iamcreasy 5y agoWhat are the drawbacks of Poetry?
- orf 5y agoIf you’re not using PyPi (think a corporate Nexus install or a private repo) then locking can be slow. But that’s not necessarily Poetry’s fault, it’s that those private servers don’t expose the complete pypi JSON api. Uhh, I’m struggling to think of anything else. It makes requirements.txt based projects feel barbaric and that will make you feel bad working with them?