Skip to content

Commit 13e24e4

Browse files
committed
Clarifications based on comments from @mgorny
* When an attempt is made to create a second session with the same name-version pair, but the first session is in `pending`, `processing`, or `complete` state, the second session is *not* created and a 409 is returned. * There's nothing special about `0.0.0` as a placeholder version, and it really should be `0.0.0a0`.
1 parent 2eb0c14 commit 13e24e4

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

peps/pep-0694.rst

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -437,10 +437,10 @@ the following keys:
437437
Multiple Session Creation Requests
438438
++++++++++++++++++++++++++++++++++
439439

440-
If a second session is created for the same name-version pair while a session for that pair is in the
441-
``pending``, ``processing``, or ``complete`` state, then the server **MUST** respond with a ``409 Conflict``
442-
and **MUST** include a ``Location`` header that points to the :ref:`session status URL
443-
<publishing-session-status>`.
440+
If a second attempt to create a session is requested for the same name-version pair while a session for that
441+
pair is in the ``pending``, ``processing``, or ``complete`` state, then a new session is *not* created.
442+
Instead, the server **MUST** respond with a ``409 Conflict`` and **MUST** include a ``Location`` header that
443+
points to the :ref:`session status URL <publishing-session-status>`.
444444

445445
For sessions in the ``error`` or ``canceled`` state, a new session is created with same ``201 Created``
446446
response and payload, except that the :ref:`publishing session status URL <publishing-session-status>`,
@@ -1015,7 +1015,8 @@ name (assuming of course that the name doesn't already exist).
10151015

10161016
To do this, :ref:`create a new publishing session <publishing-session-create>`, then :ref:`publish the session
10171017
<publishing-session-completion>` without uploading any files. While the ``version`` key is required in the
1018-
JSON body of the create session request, you can simply use the placeholder version number ``"0.0.0"``.
1018+
JSON body of the create session request, you can simply use a placeholder version number such as
1019+
``"0.0.0a0"``.
10191020

10201021
The user that created the session will become the owner of the new project.
10211022

0 commit comments

Comments
 (0)