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

Accept PEP 629 (#1782)

This commit is contained in:
Brett Cannon 2021-01-26 13:19:45 -08:00 committed by GitHub
parent e5ccf9cb7b
commit f096682452
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
pep-0629.rst
View File

@ -3,13 +3,20 @@ Title: Versioning PyPI's Simple API
Author: Donald Stufft <donald@stufft.io>
BDFL-Delegate: Brett Cannon <brett@python.org>
Discussions-To: https://discuss.python.org/t/pep-629-versioning-pypis-simple-api/4720
Status: Draft
Status: Accepted
Type: Standards Track
Content-Type: text/x-rst
Created: 16-Jul-2020
Post-History: 16-Jul-2020
.. note::
This PEP was
`accepted on 2020-08-20 <https://discuss.python.org/t/pep-629-versioning-pypis-simple-api/4720/15>`__.
It will be marked as "Final" once either PyPI supports the tag or
a library from the PyPA supports it.
Abstract
========
@ -86,7 +93,7 @@ Clients
Clients interacting with the simple API **SHOULD** introspect each
response for the repository version, and if that data does not exist
**MUST** assumee that it is version 1.0.
**MUST** assume that it is version 1.0.
When encountering a major version greater than expected, clients
**MUST** hard fail with an appropiate error message for the user.
@ -115,7 +122,7 @@ Using an URL
------------
Another traditional mechanism for versioning APIs is to bake it
into the URL, something like ``/1.0/simplee/`` or so. This works
into the URL, something like ``/1.0/simple/`` or so. This works
well for major version changes where olders clients are not
expected to be capable of continuing to use it, but it is not
well suited to minor version bumps, particularly when the version