Skip to content

Name mapping PEP: Minor editorial changes #56

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
rgommers merged 5 commits into from
Sep 3, 2025
Merged

Name mapping PEP: Minor editorial changes #56

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
39b459c
Use :pep:`NNN` instead of :doc:`pep-0NNN`
jaimergp Sep 3, 2025
e0adca7
Update email
jaimergp Sep 3, 2025
4a9439d
Open issues needs "None at this time."
jaimergp Sep 3, 2025
dc451af
Update title
jaimergp Sep 3, 2025
1aaa96a
Update date
jaimergp Sep 3, 2025
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
20 changes: 11 additions & 9 deletions peps/pep-9999.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,31 +1,31 @@
PEP: 9999
Title: A package dependency name mapping mechanism
Title: An external dependency registry and name mapping mechanism
Author: Pradyun Gedam <pradyunsg@gmail.com>,
Ralf Gommers <ralf.gommers@gmail.com>,
Michał Górny <mgorny@quansight.com>,
Jaime Rodríguez-Guerra <jrodriguez@quansight.com>,
Jaime Rodríguez-Guerra <jaime.rogue@gmail.com>,
Michael Sarahan <msarahan@gmail.com>
Discussions-To:
Status: Draft
Type: Standards Track
Topic: Packaging
Created: 22-Aug-2025
Post-History: 22-Aug-2025,
Created: 03-Sep-2025
Post-History: 03-Sep-2025,
Resolution:


Abstract
========

This PEP specifies a name mapping mechanism that allows packaging tools to map
external dependency identifiers (as introduced in :doc:`pep-0725`) to their
external dependency identifiers (as introduced in :pep:`725`) to their
counterparts in other package repositories.

Motivation
==========

Packages on PyPI often require build-time and runtime dependencies that are not
present on PyPI. :doc:`pep-0725` introduced metadata to express
present on PyPI. :pep:`725` introduced metadata to express
such dependencies. Using concrete external dependency metadata for
a Python package requires mapping the given dependency identifiers to the specifiers
used in other ecosystems, which would allow to:
Expand Down Expand Up @@ -1102,7 +1102,7 @@ Maintainers of Python projects

A package maintainer's responsibility is to decide the DepURL that best
represents the external dependency that their package needs. This is covered
in :doc:`pep-0725`; the interactive mappings browser demo located at
in :pep:`725`; the interactive mappings browser demo located at
`external-metadata-mappings.streamlit.app <https://external-metadata-mappings.streamlit.app/>`__
may come handy. The central registry documentation may include examples and
frequently asked questions to guide newcomers with their decisions.
Expand Down Expand Up @@ -1267,6 +1267,8 @@ once the central registry has matured with significant adoption.
Open Issues
===========

None at this time.

References
==========

Expand All @@ -1282,9 +1284,9 @@ In contrast with the ecosystem mappings, the central registry and the list of kn
ecosystems need to be maintained by a central authority. The authors propose to:

- Host the ``external-metadata-mappings`` and ``pyproject-external`` repositories under the PyPA_
GitHub organization (or equivalent as per :doc:`pep-0772`).
GitHub organization (or equivalent as per :pep:`772`).
- Create a maintainers team for these two repositories, seeded with the authors of this PEP and
regulated as per :doc:`pep-0772`.
regulated as per :pep:`772`.

Appendix B: Virtual versioning proposal
=======================================
Expand Down
Loading