Skip to content

Commit aa5a2df

Browse files
JacobCoffeewarsaw
andauthored
PEP 755: Mark as Withdrawn (#5162)
* PEP 755: Mark as Withdrawn * Apply suggestion from @warsaw Add a Resolution header. --------- Co-authored-by: Barry Warsaw <barry@python.org>
1 parent 37f3120 commit aa5a2df

1 file changed

Lines changed: 16 additions & 1 deletion

File tree

‎peps/pep-0755.rst‎

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,26 @@ Author: Ofek Lev <ofekmeister@gmail.com>
44
Sponsor: Barry Warsaw <barry@python.org>
55
PEP-Delegate: Dustin Ingram <di@python.org>
66
Discussions-To: https://discuss.python.org/t/63191
7-
Status: Draft
7+
Status: Withdrawn
88
Type: Process
99
Topic: Packaging
1010
Created: 05-Sep-2024
1111
Post-History: `07-Sep-2024 <https://discuss.python.org/t/63191>`__,
12+
Resolution: `02-Oct-2026 <https://discuss.python.org/t/pep-755-implicit-namespace-policy-for-pypi/63191/79>`__
13+
14+
.. withdrawn::
15+
16+
This PEP has been withdrawn. :pep:`752` defines the interoperability
17+
requirements that package repositories need in order to support namespaces;
18+
the process for applying for and reviewing namespace grants is an
19+
index-specific policy decision rather than an interoperability standard.
20+
PyPI's namespace policy will instead be published and maintained as PyPI
21+
policy by the PSF, with input from PyPI staff, the community, and, where it
22+
affects packaging interoperability, the Packaging Council. This leaves other
23+
package repositories free to set policies appropriate to them.
24+
25+
In particular, PyPI does not prioritize review of applications from paid
26+
organizations and will not do so for namespace applications.
1227

1328
Abstract
1429
========

0 commit comments

Comments
 (0)