-
Notifications
You must be signed in to change notification settings - Fork 24.9k
[build] pin setuptools>=77
to enable PEP 639
#158104
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
base: gh/XuehaiPan/365/base
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/158104
Note: Links to docs will display an error until the docs builds have been completed. ❌ 3 New Failures, 1 Unrelated FailureAs of commit 0516a50 with merge base ff0d56d ( NEW FAILURES - The following jobs have failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This reverts commit a78fb63. Reverted pytorch#158104 on behalf of https://github.com/malfet due to It still breaks inductor-perf-nightly, see https://github.com/pytorch/pytorch/actions/runs/16425364208/job/46417088208, I'm going to dismiss all previous reviews ([comment](pytorch#158104 (comment)))
I'm guessing because the pre-PEP 639 way is deprecated and That said, the version bumps can be decoupled from the licensing expression change. That will be good, because there's more to PEP 639 than just using an SPDX expression - it has to actually be the correct expression for the distribution (rather than the project's license), which given the many things PyTorch vendors will be something like:
This PR in its current state is an improvement, but not actually improving the license metadata just yet. |
@albanD, I have updated the PR description for more context #158104 (comment). |
ghstack-source-id: d8f9f75 Pull-Request: pytorch#158104
ghstack-source-id: e5138b4 Pull-Request: pytorch#158104
ghstack-source-id: 32a4865 Pull-Request: pytorch#158104
ghstack-source-id: 9a3c1e9 Pull-Request: pytorch#158104
ghstack-source-id: b1f18b3 Pull-Request: pytorch#158104
Adding |
ghstack-source-id: 8ffb2cf Pull-Request: pytorch#158104
ghstack-source-id: 79378ae Pull-Request: pytorch#158104
ghstack-source-id: 443804a Pull-Request: pytorch#158104
Since PyTorch 2.8.0 has been released, I wonder if there are any blockers or unresolved concerns about this PR? cc @albanD |
To me there are two main concers:
|
See the PR description #158104 (comment), we will need to pin either
I will try to remove the pins as much as I can in this PR, and then get back to you. |
PEP 639: peps.python.org/pep-0639
setuptools
v77 adds PEP 639 support for SPDX expression aspackage.license
inpyproject.toml
and also deprecated TOML-table-basedpackage.license
. That depression will be converted to an error in the future.Note that
setuptools<77
does not support SPDX-basedpackage.license
whilesetuptools>=77
will error for non-SPDX-basedpackage.license
in the future. We need an explicit version pin forsetuptools>=77
(or pinsetuptools<77
).See also:
project.license
deprecation if v77 unavailable pypa/setuptools#4903Stack from ghstack (oldest at bottom):
setuptools<80.0
#156049setuptools>=77
to enable PEP 639 #158104cc @malfet @seemethere @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @chauhang @amjames @Lucaskabela