-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Avoid future breakage of setup.py
invokations
#8711
Conversation
I don't understand the test failure, seems unrelated? |
Important to note that I don't think this has any downsides. Folks willing to use newer versions of setuptools for some exotic feature will need to switch to PEP-517 build system specification, which would enable pip build isolation. And even if they refuse to do that for some reason, they can always add another On the other hand, @agjohnson suggested capping the version only when |
Would be cool if we could test it with some real-world projects just be safe though. |
xref pypa/setuptools#2904 |
The test failing is related. Take a look at this line https://app.circleci.com/pipelines/github/readthedocs/readthedocs.org/3393/workflows/481df7c7-8c03-47a7-a85a-5b1e216b3202/jobs/7260?invite=true#step-106-186 It checks for the command executed and it contains |
I don't have full contex about this because there is too much things involved and too much reading required 😄 --however, it doesn't seem bad to pin setuptools to a version that works. @astrojuanlu, you are my packaging master, so if you say this is correct it is for me 😉
Did we already notice some projects failing because of this? I can help you test this if you want. |
There are no projects failing yet, because the removal hasn't happened. Hmmm I'll think of how we could test it |
Oh thanks for the pointer, there was a huge traceback and I got lost. Addressing. |
I think the only way of effectively demonstrating the effects of not merging this would be to locally replace the deprecation warnings introduced in setuptools 58.3.0 for |
The setuptools in Python 3.8 `venv` is no longer ancient, so it is not necessary to upgrade it anymore.
Added an unrelated commit, but that involves setuptools too. |
👍 we can iterate later if we need to buy ourselves more time on this deprecation |
Co-authored-by: Santos Gallegos <[email protected]>
517cc58
to
cc255e3
Compare
Co-authored-by: Santos Gallegos <[email protected]>
See #8659.