Skip to content

PEP 755: Mark as Withdrawn #5162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
warsaw merged 2 commits into from
Oct 8, 2026
Merged

PEP 755: Mark as Withdrawn #5162

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
555ca78
PEP 755: Mark as Withdrawn
JacobCoffee Oct 8, 2026
0e94820
Apply suggestion from @warsaw
warsaw Oct 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion peps/pep-0755.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,26 @@ Author: Ofek Lev <ofekmeister@gmail.com>
Sponsor: Barry Warsaw <barry@python.org>
PEP-Delegate: Dustin Ingram <di@python.org>
Discussions-To: https://discuss.python.org/t/63191
Status: Draft
Status: Withdrawn
Type: Process
Topic: Packaging
Created: 05-Sep-2024
Post-History: `07-Sep-2024 <https://discuss.python.org/t/63191>`__,
Comment thread
warsaw marked this conversation as resolved.
Resolution: `02-Oct-2026 <https://discuss.python.org/t/pep-755-implicit-namespace-policy-for-pypi/63191/79>`__

.. withdrawn::

This PEP has been withdrawn. :pep:`752` defines the interoperability
requirements that package repositories need in order to support namespaces;
the process for applying for and reviewing namespace grants is an
index-specific policy decision rather than an interoperability standard.
PyPI's namespace policy will instead be published and maintained as PyPI
policy by the PSF, with input from PyPI staff, the community, and, where it
affects packaging interoperability, the Packaging Council. This leaves other
package repositories free to set policies appropriate to them.

In particular, PyPI does not prioritize review of applications from paid
organizations and will not do so for namespace applications.

Abstract
========
Expand Down
Loading