Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please don't pin dependencies to specific versions in requirements.txt / setup.py unless absolutely required #22

Open
ackalker opened this issue May 3, 2023 · 0 comments

Comments

@ackalker
Copy link

ackalker commented May 3, 2023

Pinning exact versions of dependencies in a package published on PyPI can cause problems for people with specific requirements. Please see this StackOverflow answer for background.

In my case, my GPU version is newer than what is supported by the version of torch listed in requirements.txt / setup.py.
Also I want to use one of the PyTorch packages (python-pytorch-opt-cuda) provided by my distro (Arch Linux), even in virtualenvs, because of specific compilation options and disk space concerns.
My distro package for PyTorch also depends on a version of numpy which is incompatible with the version in requirements.txt / setup.py.

These are just some of the issues that people like me may face.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant