Skip to content

Commit 5e68dde

Browse files
potiukhugovk
andauthored
PEP 752: Updates including co-authoring of the PEP (#4292)
Co-authored-by: Hugo van Kemenade <[email protected]>
1 parent 98b61f0 commit 5e68dde

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

peps/pep-0752.rst

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
PEP: 752
22
Title: Implicit namespaces for package repositories
3-
Author: Ofek Lev <[email protected]>
3+
Author: Ofek Lev <[email protected]>,
4+
Jarek Potiuk <[email protected]>
45
Sponsor: Barry Warsaw <[email protected]>
56
PEP-Delegate: Dustin Ingram <[email protected]>
67
Discussions-To: https://discuss.python.org/t/63192
@@ -39,6 +40,9 @@ namespace. A few examples:
3940
are prefixed by ``opentelemetry-`` with child prefixes in the form
4041
``opentelemetry-<component>-<name>-``. The contrib packages live in a
4142
central repository and they are the only ones with the ability to publish.
43+
* `Apache Airflow <https://airflow.apache.org>`__ is a platform to programmatically
44+
author, schedule and monitor workflows. It has providers, where each
45+
provider package is prefixed by ``apache-airflow-providers-``.
4246

4347
__ https://github.com/open-telemetry/opentelemetry-python
4448
__ https://github.com/open-telemetry/opentelemetry-python-contrib
@@ -93,6 +97,16 @@ similar characters but that is insufficient for these use cases.
9397

9498
__ https://github.com/pypi/warehouse/blob/8615326918a180eb2652753743eac8e74f96a90b/warehouse/migrations/versions/d18d443f89f0_ultranormalize_name_function.py#L29-L42
9599

100+
Another problem that namespacing would solve is the issue of choosing new names
101+
for packages following the agreed patterns of naming. Often (this is the case
102+
for Apache Airflow for example), there are public discussions that precede
103+
the decision to create a new package. The decision is based on the agreed
104+
name and follow the pattern of the existing packages. If more package names are
105+
considered during the discussion, all the names have to be reserved via a PyPI
106+
interface before the discussion is public, otherwise the names can be taken by
107+
other users. This has happened in the past as explained
108+
in the associated `discussion <https://discuss.python.org/t/pep-752-implicit-namespaces-for-package-repositories/63192/80>`__.
109+
96110
Rationale
97111
=========
98112

0 commit comments

Comments
 (0)