[rvanlaar]

The 1.0 release is a must for a working poetry environment. The people handling it are friendly and communicate over github and discord. However, it's not all roses.

- VSCode supports poetry as a second class citizen - Documentation is there, but only in github issues - There is no migration path from pip and pipenv to poetry - I can't do releases via CI because of a poetry bug.

[duckerude]

DepHell claims to be able to convert to and from pip, pipenv and poetry, so perhaps that could be used for migrating?

https://dephell.org/docs/cmd-deps-convert.html

[kstrauser]

We love DepHell. I migrated some work repos from Pipenv (and plain ol' pip) to Poetry. However, we didn't want to have a flag day where we updated our build tooling to be 100% Poetry, so I made a Makefile target that builds requirements.txt and setup.py from pyproject.toml. Now developers can work with pleasant tooling, but the build system can use the old stuff it already knows.

We're close to having everything migrated to Poetry. When that day comes, we can throw out all the compatibility stuff, update the build server, and be happy. Until that day, DepHell gives us an easy compatibility layer so that we don't have to do the migration all at once. It's awesome.

[rvanlaar]

Ah hell, I wish I had known about this tool before migrating.

Thank you so much for pointing it out. I've added it to this issue.

https://github.com/python-poetry/poetry/issues/1701

[rbongers]

There is also a bug that is keeping me from switching, and also the handling of that bug has not been great, otherwise I would do so in a heartbeat.