State of PyPI Organizations

Packaging
41

Hi, my application to get an organisation for my company was accepted recently and I was eager to start publishing packages under my company’s namespace.

However, maybe I’m missing something, but it doesn’t seem to work as I expected.

I expected to get a namespace “abilian” (name of my company) and to be able to publish packages in this namespace (e.g. abilian/project1, abilian/project2, etc.).

However, trying to publish my first package (under my new organisation), I get the following error “This project name has already been used. Choose a different project name.”.

So I guess there is no namespacing after all ?

Or did I miss something ?

I think namespacing is really important to prevent namesquatting or even unwilling name collision. Is there any plan to implement it or has this ship already sailed ?

42

See PEP 752 and PEP 755 for current concrete proposals. Note that this is not NPM-style {organisation}/{package} namespacing.

See also this Ideas topic (2019): Namespace support in pypi

A

3 Likes
43

As of today:

  • 5,000 Pending Organization Requests, earliest 2024-05-06
    • 1,737 Community
    • 3,263 Company
  • 2,878 Approved Organizations
    • 1,101 Community
    • 1,776 Company
8 Likes