pip and virtualenv because I have always used it and have never have run into issues at scale.
Coming from a "Poetry background", this makes my life easier to not have to remember the pip/venv commands.
Are you using it to avoid Poetry for one of the use cases it doesn't handle well? (Otherwise, I don't see why one would use it.)
Of course, it could include a way to "convert" a pip-based package to Poetry, or whatnot.
Like, I know developing a package with Poetry can be painful.
And I also use pipx for use cases like running CLIs installed globally.
Or maybe you mean contributing to a third-party open-source project that doesn't use Poetry and the maintainers don't want to migrate to it for some reason.
I don't see anything like that mentioned in the readme. Maybe it would help to document the intended use cases?
In essence, I see pip as the more standardized option, given its inclusion with Python. However, I initially turned to Poetry because I prefer its commands over those of pip. What slightly disappoints me is Poetry's divergence from pip's workflow.
I appreciate your suggestion in the README! At the moment it's definitely more of a personal endeavor rather than trying to persuade anyone to use it... however, it doesn't intend to introduce anything new, it's just a CLI wrapper around standard Python tools.