-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Add build-system requirements #6230
Conversation
To make project https://peps.python.org/pep-0517/ compliant Solves pytorch/pytorch#80745
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @malfet
Hey @malfet! You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py |
|
||
[build-system] | ||
|
||
requires = ["setuptools", "torch", "wheel"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding torch
as a requirement here does only somewhat solve this:
pip
will create a separate virtual env for these requirements, which means it will pulltorch
from PyPI. That means you will get a CPU version for macOS and Windows and an outdated CUDA version (10.2 IIRC) for Linux.- We only have the stable binaries up on PyPI, but in general we depend on the current nightly.
Thus, even with this set, users could have problems building from source.
I don't have a solution for this. Just raising awareness.
Summary: To make project https://peps.python.org/pep-0517/ compliant Solves pytorch/pytorch#80745 Reviewed By: jdsgomes Differential Revision: D37643905 fbshipit-source-id: 6f20b9c38a18ed9c0c189ef377a39b88716998fe
To make project PEP-517 compliant
Solves pytorch/pytorch#80745