Text of peps.python.org › pep-0541 as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

PEP 541 – Package Index Name Retention | peps.python.org

PEP 541 – Package Index Name Retention PEP 541 – Package Index Name Retention Author : Łukasz Langa <lukasz at python.org> BDFL-Delegate : Mark Mangoba <mmangoba at python.org> Discussions-To : Distutils-SIG list Status : Final Type : Process Topic : Packaging Created : 12-Jan-2017 Post-History : Resolution : Distutils-SIG message Table of Contents Abstract Rationale Approval Process Specification Implementation Reachability Abandoned projects Continued maintenance of an abandoned project Removal of an abandoned project Name conflict resolution for active projects Invalid projects Intellectual property policy The role of the Python Software Foundation How to request a name transfer Prior art Rejected Proposals References Copyright Acknowledgements Abstract This PEP proposes an extension to the Terms of Use [1] of the Package Index [2] , clarifying expectations of package owners regarding ownership of a package name on the Package Index, specifically with regards to conflict resolution.

Existing package repositories such as CPAN [3] , NPM [4] , and GitHub [5] will be investigated as prior art in this field. Rationale Given that package names on the Index are sharing a single flat namespace, a unique name is a finite resource. The growing age of the Package Index causes a constant rise of situations of conflict between the current use of the name and a different suggested use of the same name. This document aims to provide general guidelines for solving the most typical cases of such conflicts.

Approval Process As the application of this policy has potential legal ramifications for the Python Software Foundation, the approval process used is more formal than that used for most PEPs. Rather than accepting the PEP directly, the assigned BDFL-Delegate will instead recommend its acceptance to the PSF’s Packaging Working Group. After consultation with the PSF’s General Counsel, adoption of the policy will then be subject to a formal vote within the working group.

This formal approval process will be used for both initial adoption of the policy, and for adoption of any future amendments. Specification The main idea behind this document is that the Package Index serves the community. Every user is invited to upload content to the Package Index under the Terms of Use, understanding that it is at the sole risk of the user. While the Package Index is not a backup service, the maintainers of the Package Index do their best to keep that content accessible indefinitely in its published form.

However, in certain edge cases the greater community’s needs might overweigh the individual’s expectation of ownership of a package name. The use cases covered by this document are: Abandoned projects: continued maintenance by a different set of users; or removal from the Index for use with a different project. Active projects: resolving disputes over a name. Invalid projects: projects subject to a claim of intellectual property infringement.

The proposed extension to the Terms of Use, as expressed in the Implementation section, will be published as a separate document on the Package Index, linked next to existing Terms of Use in the front page footer. Implementation Reachability The user of the Package Index is solely responsible for being reachable by the Package Index maintainers for matters concerning projects that the user owns. In every case where contacting the user is necessary, the maintainers will try to do so at least three times, using the following means of contact: the e-mail address on file in the user’s profile on the Package Index; the e-mail address listed in the Author field for a given project uploaded to the Index; and any e-mail addresses found in the given project’s documentation on the Index or on the listed Home Page.

The maintainers stop trying to reach the user after six weeks. Abandoned projects A project is considered abandoned when ALL of the following are met: owner not reachable (see Reachability above); no releases within the past twelve months; and no activity from the owner on the project’s home page (or no home page listed). All other projects are considered active . Continued maintenance of an abandoned project If a candidate appears willing to continue maintenance on an abandoned project, ownership of the name is transferred when ALL of the following are met: the project has been determined abandoned by the rules described above; the candidate is able to demonstrate their own failed attempts to contact the existing owner; the candidate is able to demonstrate improvements made on the candidate’s own fork of the project; the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround; and the maintainers of the Package Index don’t have any additional reservations.

Under no circumstances will a name be reassigned against the wishes of a reachable owner. Removal of an abandoned project Projects are never removed from the Package Index solely on the basis of abandonment. Artifacts uploaded to the Package Index hold inherent historical value. An abandoned project can be transferred to a new owner for purposes of reusing the name when ALL of the following are met: the project has been determined abandoned by the rules described above; the candidate is able to demonstrate their own failed attempts to contact the existing owner; the candidate is able to demonstrate that the project suggested to reuse the name already exists and meets notability requirements; the candidate is able to demonstrate why a fork under a different name is not an acceptable workaround; download statistics on the Package Index for the existing package indicate project is not being used; and the maintainers of the Package Index don’t have any additional reservations.

Name conflict resolution for active projects The maintainers of the Package Index are not arbiters in disputes around active projects. There are many possible scenarios here, a non-exclusive list describing some real-world examples is presented below. None of the following qualify for package name ownership transfer: User A and User B share project X. After some time they part ways and each of them wants to continue the project under name X.

User A owns a project X outside the Package Index. User B creates a package under the name X on the Index. After some time, User A wants to publish project X on the Index but realizes name is taken. This is true even if User A’s project X gains notability and the User B’s project X is not notable. User A publishes project X to the Package Index. After some time User B proposes bug fixes to the project but no new release is published by User A.

This is true even if User A agrees to publish a new version and later doesn’t, even if User B’s changes are merged to the source code repository for project X. Again, the list above is not exclusive. The maintainers of the Package Index recommend users to get in touch with each other and solve the issue by respectful communication (see the PSF Code of Conduct [6] ). Invalid projects A project published on the Package Index meeting ANY of the following is considered invalid and will be removed from the Index: project does not conform to Terms of Use; project is malware (designed to exploit or harm systems or users directly, to facilitate command-and-control attacks, or perform data exfiltration); project is spam (designed to advertise or solicit goods or services); project contains illegal content; project violates copyright, trademarks, patents, or licenses; project is name squatting (package has no functionality or is empty); project name, description, or content violates the Code of Conduct; project uses obfuscation to hide or mask functionality; or project is abusing the Package Index for purposes it was not intended.

The Package Index maintainers pre-emptively declare certain package names as unavailable for security reasons. Intellectual property policy It is

The rest of this page is on the live site.