File tree Expand file tree Collapse file tree 2 files changed +25
-0
lines changed
Expand file tree Collapse file tree 2 files changed +25
-0
lines changed Original file line number Diff line number Diff line change 200200 "github" : ("https://github.com/%s" , "%s" ),
201201 "github-user" : ("https://github.com/%s" , "@%s" ),
202202 "pypi" : ("https://pypi.org/project/%s/" , "%s" ),
203+ "pypi-org" : ("https://pypi.org/org/%s/" , "%s" ),
203204}
204205
205206# sphinxext-opengraph config
Original file line number Diff line number Diff line change @@ -370,6 +370,30 @@ administrators) to merge changes to that branch.
370370Multi-Factor Authentication must be enabled by the user in order to retain
371371access as a Release Manager of the branch.
372372
373+ PyPI organization policy
374+ ^^^^^^^^^^^^^^^^^^^^^^^^
375+
376+ The Python core team owns the :pypi-org: `cpython ` and :pypi-org: `python `
377+ organizations on PyPI for publishing packages.
378+ The main benefits of adding packages to these organizations:
379+
380+ * Visibility: we can see our packages under a PyPI org page
381+ * Maintainability: we can share granular PyPI access to improve the bus factor
382+
383+ The general policy on which organization to use:
384+
385+ * :pypi-org: `cpython `:
386+ for development tools that are tied fairly closely to CPython development.
387+ For example, :pypi: `blurb ` and :pypi: `cherry-picker `.
388+ Users generally shouldn’t have to care except for developing CPython itself
389+ (although that doesn’t mean the tools necessarily have to be unusable for
390+ anyone else).
391+ * :pypi-org: `python `:
392+ for general-audience projects that are maintained by the Python core team.
393+ For example, :pypi: `pyperformance `, :pypi: `python-docs-theme ` and
394+ :pypi: `tzdata `.
395+
396+
373397Governance
374398----------
375399
You can’t perform that action at this time.
0 commit comments