[issue40132] Mechanism to control who owns package names on PyPI?

2020-04-03 Thread Terry J. Reedy
Terry J. Reedy added the comment: PyPI is a separate project from CPython and has its own repository, tracker, and developers. -- nosy: +terry.reedy resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker

[issue40132] Mechanism to control who owns package names on PyPI?

2020-04-03 Thread ChrisRands
ChrisRands added the comment: Thanks Rémi, I missed that in PEP 541. I am still concerned that PyPI may become saturated with unmaintained packages (it is already common that one's preferred package name is taken). However, the guidance is already clear, and I guess anything stronger, like

[issue40132] Mechanism to control who owns package names on PyPI?

2020-04-01 Thread Rémi Lapeyre
Rémi Lapeyre added the comment: Hi Chris, this is explicitly forbidden in the Terms of use of Pypi and the PEP 451 at https://www.python.org/dev/peps/pep-0541/#invalid-projects: > Invalid projects > A project published on the Package Index meeting ANY of the following is > considered

[issue40132] Mechanism to control who owns package names on PyPI?

2020-04-01 Thread ChrisRands
New submission from ChrisRands : Not sure if this is the right place to mention this (apologies if not). Naturally, package names are unique so when you run `pip install package-name` there is no ambiguity. However, this means that package names are limited and potentially valuable. Already