Skip to content
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

Discuss: Support Core Metadata Mirroring #1124

Open
cooperlees opened this issue May 5, 2022 · 1 comment
Open

Discuss: Support Core Metadata Mirroring #1124

cooperlees opened this issue May 5, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@cooperlees
Copy link
Contributor

cooperlees commented May 5, 2022

PEP 658 specifies serving core package metadata from an index. Lets look at best ways to potentially mirror this if there is a sane way.

For more info: https://peps.python.org/pep-0658/

Ideas

  • Does bandersnatch have a config option to pull down the files to be statically served
  • Should this be left to the mirror service to pull the files out of the downloaded binaries and cached?

Other ideas?

@cooperlees cooperlees added the enhancement New feature or request label May 5, 2022
@pombredanne
Copy link

@cooperlees Hi :)

Does bandersnatch have a config option to pull down the files to be statically served
Should this be left to the mirror service to pull the files out of the downloaded binaries and cached?

I could see a config named metadata similar to the release-files and json and essentially have the same behaviour as json.

An alternative is to deprecate the json config and have a new json-and-metadata config that would pull both or none and could have this documentation:

The mirror json-and-metadata setting is a boolean (true/false) setting that indicates that the json packaging metadata and the core metadata (pep-0658) should be mirrored in addition to the packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants