Request "python" organisation on PyPI

[hugovk (Hugo van Kemenade)]

I don’t mind too much either way, but python-docs-theme README does point out

Note that when adopting this theme, you’re also borrowing an element of the trust and credibility established by the CPython core developers over the years. That’s fine, and you’re welcome to do so for other Python community projects if you so choose, but please keep in mind that in doing so you’re also choosing to accept some of the responsibility for maintaining that collective trust.

I think that tips it more towards the cpython side in the following categorisation?

@thomas

• 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.

Anyway, let’s start with more obvious ones, like cherry-picker → cpython: python/cherry-picker#142.