Move to PyPA org on PyPI?
With the orgs feature on PyPI, there's a PyPA org that exists already — https://pypi.org/org/pypa/. Why not make use of it?
UPD: Dustin explained the implications as an FAQ in the ML: https://mail.python.org/archives/list/[email protected]/thread/E6MWIHEK3M232UILXGQFYPHGJHF7VYW7/.
See https://github.com/pypa/pip/issues/12250#issuecomment-1698025213 -- let's hold off on this.
Why not make use of it?
Why make use of it?
As no arguments whatsoever were posted here I propose to close this issue - and open new one only if there are clear benefits outweighting negatives.
https://github.com/pypa/pip/issues/12250#issuecomment-1698025213 identified some negatives. And "it can be done" or "feature exists" is not a good reason by itself to do anything.
In the other issue Henry said that he'd like to move.
Yes, I've just started using orgs for Scikit-HEP and I think it's nice; we have a GitHub org, having a PyPI org matching it makes sense.
@henryiii so add @di as an owner?
I was hoping for at least one other maintainer to +1. Specifically @gaborbernat, @layday, and @FFY00 are on PyPI, so +1 from them would be good. IMO, this is the same as the GitHub pypa org, so anything in the GitHub org might as well be in the PyPA org.
I don't mind - making the project's affiliation to the PyPA clearer on PyPI sounds like a plus. I'm a fan of package namespaces personally, and this is as close as we can get.
Done!