-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to PyPA org on PyPI? #714
Comments
Honestly, I personally wasn't aware of the org account existed. I'm personally fine with it, although the PyPA council discussion might influence this a bit. |
It's a relatively new thing. Since the orgs were first announced during PyCon in the spring. I suppose each project should decide if they want this (like pip-audit: pypa/pip-audit#667 (comment)), but from the end-user perspective, having a visual reassurance is a good thing. |
IMO we should wait on this until the whole PyPA council discussion wraps up. |
In the ML? |
Yea, on discuss.python.org. |
See pypa/pip#12250 (comment) -- let's hold off on this. |
@brettcannon Dustin posted some details here: https://mail.python.org/archives/list/pypa-committers@python.org/thread/E6MWIHEK3M232UILXGQFYPHGJHF7VYW7/. |
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/pypa-committers@python.org/thread/E6MWIHEK3M232UILXGQFYPHGJHF7VYW7/.
The text was updated successfully, but these errors were encountered: