[dhruvkar]

I've been watching poetry for the last couple years, hoping that it is THE replacement to the virtualenv/virtualenvwrapper/pyenv workflow.

pipenv never felt quite right. poetry has felt really close.

I'd love to know if anyone has made this jump and their experience.

[siddboots]

Same here. I got really excited by pipenv, but every single time I've tried it, it takes 10+ minutes to determine the dependencies and build a lock file (see issue 2284 [1]). It just makes it un-usable for a lot of my use-cases, e.g. setting up a clean environment for exploratory data analysis. Does anyone know if poetry improves in this area?

[1] https://github.com/pypa/pipenv/issues/2284

[hobofan]

(See my other comment)

Yes, I haven't encountered any of the slowness in dependency resolution that Pipenv has with Poetry. It does still feel a bit slow compared to package managers from other languages, but not in a buggy way, so I would attribute it to not being that optimized yet.

[hobofan]

Same here. Been using Poetry for a few months, and it's been a blast!

Before that I tried to use pipenv, but it's been too buggy and unpredictably slow with installs. I've always had bad experiences with virtualenv etc., and mostly stayed away from Python development due to that. With Poetry that has changed immensely, as I now have the reproducibility in environment I'm used to from Rust/Ruby/Node.

All that said, I think there is still quite a way to go for Poetry. E.g. I had (hard to reproduce) bugs where if the install was canceled, I had to purge the whole virtualenv, as it was unable to recover itself. I'm pretty opimistic about the project as a whole though!