If I come across a package that relies on pip, and I intend to fork it, introduce changes that might affect the requirements.txt file, and potentially submit a

If I come across a package that relies on pip, and I intend to fork it, introduce changes that might affect the requirements.txt file, and potentially submit a pull request to the original repository, I find it more straightforward to stick with pip itself. This is because Poetry, while versatile, doesn't seamlessly integrate with requirements.txt (it can be configured to work with it, but it doesn't write back to it). 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.