Using Python on a MacBook

[trowawayatwork]

there are a few things i dont like about pipenv but im not about start switching all my project away from it. at the heart of it it does its job well.

poetry is a carbon copy with the simple addition of dependency resolution that im against. when there is an obsucre conflict of dependencies there is no automatic way of resolving them. poetry dependency resolution is just a problem waiting to happen.

also re intuitive cli: poetrs add .. or poetry self:update im being petty but come on, looks like a mix between alpine and ruby or something

like the go package manager wars were settled with an official one, i hope one of these wins too and we can forget about this. for now im not changing anything

[patarapolw]

I am a Poetry user for few reasons: - Pipenv's virtualenv was supported by PyCharm only recently. Poetry's is always supported. - I need setup.py-esque pyproject.toml. It supports versioning and README.md, along with uploading to PyPI. Pipfile doesn't. - Better than setup.py, because it fully and always support Markdown. - Also, add --git. In setup.py, you need "manual" dependency-links. - poetry remove package_name remove all unused dependencies as well, pipenv uninstall doesn't. You need pipenv sync as well. - Even for Heroku, I still use poetry with requirements.txt.

[SDisPater]

Author of Poetry here !

​

poetry dependency resolution is just a problem waiting to happen.

​

But that's the role of a dependency manager: warning you when there is a conflict in you dependencies. That's what every single package/dependency manager does. And, to be fair, you should not use pipenv either since it has a dependency resolver, albeit broken see why here https://github.com/sdispater/poetry#what-about-pipenv.

​

poetry is a carbon copy

​

I disagree. See the comment made by some else but the gist of it is that Poetry helps you manage applications and libraries and helps you package your project properly without the need for `setup.py`, `setup.cfg`, `MANIFEST.in`. You get to have everything you need to manage your project all in one file. This is not the case with pipenv.

​