Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider leaving poetry #13

Open
cdcarter opened this issue Dec 24, 2018 · 0 comments
Open

Consider leaving poetry #13

cdcarter opened this issue Dec 24, 2018 · 0 comments

Comments

@cdcarter
Copy link
Contributor

I've been trying to give poetry a fair chance, but keep running into weird issues. Poetry-setup seems to be interfering with ideal usage (try pip install poetry poetry-setup && poetry install in a fresh venv now 😢 ), but we want that for pip install. I can spin out an issue about that but...

So, despite pyproject.toml being something I really like (and the configuration philosophy of poetry in general being very appealing), the actual implementation and ecosystem feels not-quite-there.

It seems like there are three major players right now:

  • pip/setuptools
  • poetry
  • pipenv

Only pip has standard library "support". The other two are not quite-competing, and have much lower adoption rates. They both have bootstrap concerns (especially on our deployment hosts).

I don't mind adopting new technologies, but this edge feels bloody. Losing the additional dev deps is just a little win.

I'll ask for actual feedback on this after the holiday, and give myself a few more days for poetry to convince me...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant