From f096682452f36cbf1c7d018f15e11a41078b4659 Mon Sep 17 00:00:00 2001 From: Brett Cannon Date: Tue, 26 Jan 2021 13:19:45 -0800 Subject: [PATCH] Accept PEP 629 (#1782) --- pep-0629.rst | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/pep-0629.rst b/pep-0629.rst index 4e59530f9..b37a1a6e0 100644 --- a/pep-0629.rst +++ b/pep-0629.rst @@ -3,13 +3,20 @@ Title: Versioning PyPI's Simple API Author: Donald Stufft BDFL-Delegate: Brett Cannon 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 `__. + 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