-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Include most recent upload metadata when uploading to PyPI #1381
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
Comments
Indeed, this is true. However, I'm not sure it's worth doing what it would take to support Metadata 2.1 on upload. I think it makes more sense just to deprecate |
I'll take a look at how difficult it would be to do next week. One big problem is that this is creating a lot of bad and immutable data on PyPI and a lot of people are just running scripts they wrote a long time ago or copying from some old "how to make a release" guide someone made. If we're going to say that the new upload metadata is just not supported in setuptools, we should probably start throwing an actual error rather than a warning. I think the options are:
I think 3 is too clever and from the cursory look I made at the code before I created this issue, I think 2 is a feasible path forward. |
I'm for 1: we should deprecate and remove support for |
#1410 is merged/released, I think this issue can be closed. |
I think we should keep this open until the upload/register commands are completely removed. |
Fair enough, we should probably revise the original issue in that case. |
I'm actually planning on fixing this at some point, because it's currently polluting PyPI with bad packages in a very insidious way, as a major driver of this issue. If we proactively remove the The patch was decently simple last time I checked, it's just that the bug is in |
looking at this |
Previously this value was hard-coded to '1.0', which was inaccurate for many packages. Fixes pypa#1381
Previously this value was hard-coded to '1.0', which was inaccurate for many packages. Fixes pypa#1381
Previously this value was hard-coded to '1.0', which was inaccurate for many packages. Fixes pypa#1381
Previously this value was hard-coded to '1.0', which was inaccurate for many packages. Fixes pypa#1381
Previously this value was hard-coded to '1.0', which was inaccurate for many packages. Fixes pypa#1381
Previously this value was hard-coded to '1.0', which was inaccurate for many packages. Fixes pypa#1381
Previously this value was hard-coded to '1.0', which was inaccurate for many packages. Fixes pypa#1381
Previously this value was hard-coded to '1.0', which was inaccurate for many packages. Fixes pypa#1381
The upload and register commands were deprecated over a year ago, in July 2019 (PR pypaGH-1410, discussed in issue pypaGH-1381). It is time to actively remove them in favor of twine.
The upload and register commands were deprecated over a year ago, in July 2019 (PR pypaGH-1410, discussed in issue pypaGH-1381). It is time to actively remove them in favor of twine.
The upload and register commands were deprecated over a year ago, in July 2019 (PR pypaGH-1410, discussed in issue pypaGH-1381). It is time to actively remove them in favor of twine.
The upload and register commands were deprecated over a year ago, in July 2018 (PR pypaGH-1410, discussed in issue pypaGH-1381). It is time to actively remove them in favor of twine.
The upload and register commands were deprecated over a year ago, in July 2018 (PR pypaGH-1410, discussed in issue pypaGH-1381). It is time to actively remove them in favor of twine.
The upload and register commands were deprecated over a year ago, in July 2018 (PR pypaGH-1410, discussed in issue pypaGH-1381). It is time to actively remove them in favor of twine.
The upload and register commands were deprecated over a year ago, in July 2018 (PR pypaGH-1410, discussed in issue pypaGH-1381). It is time to actively remove them in favor of twine.
The upload and register commands were deprecated over a year ago, in July 2018 (PR pypaGH-1410, discussed in issue pypaGH-1381). It is time to actively remove them in favor of twine.
It seems that for the
upload
command, we're delegating entirely todistutils
, which hasmetadata_version
hard-coded as "1.0", and only uploads the 1.0 metadata. I think this is one reason that Requires-Python data isn't showing up on PyPI.Although
setup.py upload
is basically deprecated, I think we should probably still make these improvements, even if as part of this we also addDeprecationWarning
telling people to start usingtwine
.The text was updated successfully, but these errors were encountered: