-
Notifications
You must be signed in to change notification settings - Fork 1k
Cannot Update My Packages #2342
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
Comments
Even worse, while updating through the legacy site I get a This is a small nightmare. |
Can anybody explain to me what's happening with these issues? I need to update a package that a lot of people depend on and right now I can't. |
The index at https://pypi.org/ is a pre-production deployment of Warehouse. Work on making Warehouse have feature-parity with the legacy index is currently in progress, and thus it is essentially view-only, so any "administrative" edits still need to be done through the legacy index here: https://pypi.python.org/ EDIT: This does not include editing a description --
I'm assuming here you mean the index at https://pypi.python.org/. I'm not as familiar with the legacy code base and I don't know what this error means. The right place to report a specific issue with it is here: https://github.com/pypa/pypi-legacy
I'm not exactly sure what command you ran to produce this, but I'm guessing it was
|
Pushes have been failing lately (and not just taking a few hours/days to finish as they used to). It's most likely due to this: * https://mail.python.org/pipermail/distutils-sig/2017-June/030766.html * https://packaging.python.org/guides/migrating-to-pypi-org/#uploading * pypi/warehouse#2342
I'm going to close this issue as it seems to simply be a case of confusion, and there doesn't seem to be anything more actionable on it beyond what @di has already mentioned. |
I've logged into the new system to try to update one of my packages. It shows that I am logged in and that these are my packages, but there is no menu or interface to administer them. What's happening here?
The text was updated successfully, but these errors were encountered: