You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cpython: for development tools that are tied fairly closely to CPython development. This could for example include blurb and cherry-picker. Users generally shouldn’t have to care except for developing CPython itself (although that doesn’t mean the tools necessarily have to be unusable for anyone else).
python: for general-audience projects that are maintained the Python Core Devs. An example for this category would be tzdata.
Following https://discuss.python.org/t/request-python-organisation-on-pypi/26545, we now have two organisations on PyPI: https://pypi.org/org/cpython/ and https://pypi.org/org/python/
We can add the
pyperf
PyPI project to one of the organisations.The main benefits are:
Visibility: we'll be able to see our packages under a PyPI org page
Maintainability: we can share granular PyPI access to improve the bus factor
Would you like to add this package to one of the orgs?
We should follow the SC's categorisation when deciding which one to use:
pyperformance
was added to thepython
org via python/pyperformance#370, and @diegorusso suggested there thatpyperf
would fit inpython
.I know this repo is under https://github.com/psf/ and not https://github.com/python/ on GitHub, but I don't think that matters here?
The text was updated successfully, but these errors were encountered: