-
Notifications
You must be signed in to change notification settings - Fork 209
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
Support PEP 658 metadata file hosting #1456
Comments
Oh and the juicy part, if you use bleeding-edge Something like Note that PyPI is looking into backporting the metadata hosting to older wheels but hasn't yet (which is why I decided to use |
See PEP 658.
But TL;DR: Now indexes can opt-in to also hosting a package's metadata alongside the package so that package managers don't have to download the package (which in the case of PyTorch can be >GB) to simply resolve metadata (e.g. "what packages do you depend on?").
The support looks roughly like:
data-core-metadata
attribute.true
to say "yup, I support this"sha256=deadbeef
<whl name>.metadata
.As an example from PyPI. If you go to https://pypi.org/simple/requests/ and look at the HTML you'll find:
(Note that there's two attributes with similar names due to a nasty bug in pip requiring a rename of the attribute. See PEP 714. I assume PyPI is simply just exposing both (something this index could do as well)
Then, since
data-core-metadata
exists, voilà! https://files.pythonhosted.org/packages/70/8e/0e2d847013cb52cd35b38c009bb167a1a26b2ce6cd6965bf26b47bc0bf44/requests-2.31.0-py3-none-any.whl.metadataNote that this is related-to, but not quite the same as #1347, which is specifically for sha256 PEP 503 support.
The text was updated successfully, but these errors were encountered: