HTTPX designated as critical on PyPI #2299
Replies: 3 comments 5 replies
-
I thought being part of encode required 2fa, I dont think I had it before |
Beta Was this translation helpful? Give feedback.
-
I have never released anything on PyPI so I have no idea how that is structured. I guess that either there is a single account that has publishing rights on PyPI, and to which encode/operations have access, or each member of encode/operations has their own account, that has publishing rights on PyPI? |
Beta Was this translation helpful? Give feedback.
-
I guess that's the case. cc @tomchristie |
Beta Was this translation helpful? Give feedback.
-
Hi @encode/maintainers,
Ive just received an email today from PyPI indicating HTTPX has been designated as a “critical project”.
The impact seems to be: 2FA must be enabled to “add new releases or manage the project”.
Tweet: https://twitter.com/pypi/status/1545455297388584960
I’m raising this discussion to discuss potential changes this induces for us.
As I understand we create releases through a PyPI token. Does this mean the account attached to the token has to enable 2FA so we can create further releases?
On my end, I can see I cannot access the “Manage” section (button disabled) for httpx on PyPI anymore, presumably until I enable 2FA.
Beta Was this translation helpful? Give feedback.
All reactions