We have moved our dependency management from pipenv to poetry and hasn’t been more happier than now working with and publish Python modules.

Now we use pyenv with poetry to run all our projects in Python with venv in project instead of decided by poetry default settings. We changed the settings with:

  poetry config settings.virtualenvs.in-project true

After this in hgignore or gitignore added .venv folder.

Now everything is the way we wanted, with Pipenv many times faced issues that the project worked with requirements.txt but not in Pipenv. Didn’t have this issue moving to poetry yet.

Also with emacs support and automated deployment tools the predictability of poetry made our team easy to work with and publish Python application modules.