-
Notifications
You must be signed in to change notification settings - Fork 23.2k
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 platform markers for linux only extra_install_requires #88826
Add platform markers for linux only extra_install_requires #88826
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/88826
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 3 FailuresAs of commit 9d8956b: The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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
This PR fixes a huge nuisance for me, can I do something to help push this PR through? |
we need to attach ciflow/binaries_wheel label and produce the new wheel. Once this wheel is build it needs to be tested. If it works, we can ship this PR |
I think the test failures are flakes / unrelated ( |
Tested the resulting binary installation worked:
Smoke test passed:
Metadata looks good as well:
|
@pytorchbot merge -f "Test failures are not related" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Can we cut a patch release that includes this fix? Would really help with package managers like |
… torch to ~1.12.1 again because of platform issue: pytorch/pytorch#88826
…8826) Fixes pytorch#88049 pytorch#85097 added new extra dependencies on `nvidia-*`. They are linux (GPU) only packages, but were not marked as such, causing issues installing pytorch 1.13 via Poetry (and possibly other tools that follow PyPI's metadata API) on non-Linux systems. This "fixes" the issue by adding the `; platform_system = 'Linux'` marker on these dependencies, but the main problem of different metadata for different wheels is a [somewhat larger issue](pytorch#88049 (comment)). pytorch#85097 used `;` as a delimiter for splitting the different deps, but that is the delimiter used in markers, so I changed to split on `|`. Pull Request resolved: pytorch#88826 Approved by: https://github.com/neersighted, https://github.com/lalmei, https://github.com/malfet
…8826) Fixes pytorch#88049 pytorch#85097 added new extra dependencies on `nvidia-*`. They are linux (GPU) only packages, but were not marked as such, causing issues installing pytorch 1.13 via Poetry (and possibly other tools that follow PyPI's metadata API) on non-Linux systems. This "fixes" the issue by adding the `; platform_system = 'Linux'` marker on these dependencies, but the main problem of different metadata for different wheels is a [somewhat larger issue](pytorch#88049 (comment)). pytorch#85097 used `;` as a delimiter for splitting the different deps, but that is the delimiter used in markers, so I changed to split on `|`. Pull Request resolved: pytorch#88826 Approved by: https://github.com/neersighted, https://github.com/lalmei, https://github.com/malfet
…89924) Fixes #88049 #85097 added new extra dependencies on `nvidia-*`. They are linux (GPU) only packages, but were not marked as such, causing issues installing pytorch 1.13 via Poetry (and possibly other tools that follow PyPI's metadata API) on non-Linux systems. This "fixes" the issue by adding the `; platform_system = 'Linux'` marker on these dependencies, but the main problem of different metadata for different wheels is a [somewhat larger issue](#88049 (comment)). #85097 used `;` as a delimiter for splitting the different deps, but that is the delimiter used in markers, so I changed to split on `|`. Pull Request resolved: #88826 Approved by: https://github.com/neersighted, https://github.com/lalmei, https://github.com/malfet Co-authored-by: Jacob Hayes <jacob.r.hayes@gmail.com>
…8826) Fixes pytorch#88049 pytorch#85097 added new extra dependencies on `nvidia-*`. They are linux (GPU) only packages, but were not marked as such, causing issues installing pytorch 1.13 via Poetry (and possibly other tools that follow PyPI's metadata API) on non-Linux systems. This "fixes" the issue by adding the `; platform_system = 'Linux'` marker on these dependencies, but the main problem of different metadata for different wheels is a [somewhat larger issue](pytorch#88049 (comment)). pytorch#85097 used `;` as a delimiter for splitting the different deps, but that is the delimiter used in markers, so I changed to split on `|`. Pull Request resolved: pytorch#88826 Approved by: https://github.com/neersighted, https://github.com/lalmei, https://github.com/malfet
NOTE: This fix does not address |
This looks related to this open PR #91083, but the change doesn't seem to work out just yet |
@huydhn in my system it works setting the version to >=1.3.1, can you confirm it does not work for you in that case? |
Fixes #88049
#85097 added new extra dependencies on
nvidia-*
. They are linux (GPU) only packages, but were not marked as such, causing issues installing pytorch 1.13 via Poetry (and possibly other tools that follow PyPI's metadata API) on non-Linux systems. This "fixes" the issue by adding the; platform_system = 'Linux'
marker on these dependencies, but the main problem of different metadata for different wheels is a somewhat larger issue.#85097 used
;
as a delimiter for splitting the different deps, but that is the delimiter used in markers, so I changed to split on|
.