I use Pipenv now for applications that I’m not publishing to PyPI. I like the workflow better, and find it to be much less buggy. Pipenv is not really involved

I use Pipenv now for applications that I’m not publishing to PyPI. I like the workflow better, and find it to be much less buggy. Pipenv is not really involved in package building, though. For libraries and OpenSource that I’m building actual packages for, Poetry seems nicer to me than setup.py. I’m trying it out now with one, partly to adopt the newer pyproject.toml thing. Packaging has always been kind of an ever changing mess in Python vs newer ecosystems, and I don’t see an end to that. I’d just do what works best for you. Also, the general opinionated aggressiveness of the maintainer/project is a little off putting to me. Its a little weird in the community. Normally projects don’t dog other projects on their page. Often they cite alternatives with maybe a statement on how the philosophies vary. But that’s just my opinion and experience. I’m sure others differ.