iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 708: Grammar Fixes and Clarification (#3165) 

PEP 708: Address feedback
This commit is contained in:
Donald Stufft 2023-06-09 00:52:28 -04:00 committed by GitHub
parent e815d90c2f
commit c3d9f8a3ae
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
pep-0708.rst
View File

@ -167,7 +167,7 @@ repository or repositories by adding the URLs of the project and repositories
that it is extending. that it is extending.
This is exposed in JSON as the key ``meta.tracks`` and in HTML as a meta element This is exposed in JSON as the key ``meta.tracks`` and in HTML as a meta element
named ``pypi:tracks``. named ``pypi:tracks`` on the project specific URLs, (``$root/$project/``).
There are a few key properties that **MUST** be preserved when using this There are a few key properties that **MUST** be preserved when using this
@ -181,16 +181,16 @@ metadata:
like hosted repository services where one entity operates the software but like hosted repository services where one entity operates the software but
another owns/manages the entire namespace of that repository. another owns/manages the entire namespace of that repository.
- All URLs **MUST** represent the same "project" as the project at in the - All URLs **MUST** represent the same "project" as the project in the extending
extending repository. repository.
- This does not mean that they need to serve the same files. It is valid for it - This does not mean that they need to serve the same files. It is valid for
to include binaries built on different platforms, copies with local patches them to include binaries built on different platforms, copies with local
being applied, etc. This is purposefully left vague as it's ultimately up to patches being applied, etc. This is purposefully left vague as it's
the expectations that the users have of the repository and its operators ultimately up to the expectations that the users have of the repository and
what exactly constitutes the "same" project. its operators what exactly constitutes the "same" project.
- It **MUST** point to the repositories that "owns" the namespaces, not another - It **MUST** point to the repositories that "own" the namespaces, not another
repository that is also tracking that namespace. repository that is also tracking that namespace.
- It **MUST** point to a project with the exact same name (after normalization). - It **MUST** point to a project with the exact same name (after normalization).