|
1 | 1 | PEP: 752
|
2 | 2 | Title: Implicit namespaces for package repositories
|
3 |
| -Author: Ofek Lev < [email protected]> |
| 3 | +Author: Ofek Lev < [email protected]>, |
| 4 | + |
4 | 5 | Sponsor: Barry Warsaw < [email protected]>
|
5 | 6 | PEP-Delegate: Dustin Ingram < [email protected]>
|
6 | 7 | Discussions-To: https://discuss.python.org/t/63192
|
@@ -39,6 +40,9 @@ namespace. A few examples:
|
39 | 40 | are prefixed by ``opentelemetry-`` with child prefixes in the form
|
40 | 41 | ``opentelemetry-<component>-<name>-``. The contrib packages live in a
|
41 | 42 | 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-``. |
42 | 46 |
|
43 | 47 | __ https://github.com/open-telemetry/opentelemetry-python
|
44 | 48 | __ https://github.com/open-telemetry/opentelemetry-python-contrib
|
@@ -93,6 +97,16 @@ similar characters but that is insufficient for these use cases.
|
93 | 97 |
|
94 | 98 | __ https://github.com/pypi/warehouse/blob/8615326918a180eb2652753743eac8e74f96a90b/warehouse/migrations/versions/d18d443f89f0_ultranormalize_name_function.py#L29-L42
|
95 | 99 |
|
| 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 | + |
96 | 110 | Rationale
|
97 | 111 | =========
|
98 | 112 |
|
|
0 commit comments