Don't pin unless it's needed.
I have a library… most downloaded version is 3 years old. The newer versions are massively faster but nobody uses them.
I have a library… most downloaded version is 3 years old. The newer versions are massively faster but nobody uses them.
But it’s totally reasonable to pin the private requirements that you develop it against (listed in requirements.txt, poetry.lock, or similar), updating them every so often during the course of development, so that contributors can use a consistent set of tools.
> For your dependency/versioning issue, use a virtualenv per-project and pin your dependency versions in requirements.txt
requirements.txt is not uploaded to PyPI and has no effect on your package’s dependencies when a user installs it (leaf package or no). It’s only used for developing the package itself, typically in a unique virtual environment.