Skip to content
This repository has been archived by the owner on May 30, 2020. It is now read-only.

Cannot upload package to PyPI, Have done due diligence, Think it's a bug #677

Closed
wpm opened this issue Aug 2, 2017 · 3 comments
Closed
Labels
PEP 541 Issues blocked on the implementation of PEP 541

Comments

@wpm
Copy link

wpm commented Aug 2, 2017

I have a pure Python package named Mycroft that I am trying to register and upload to PyPI.

When I try to register either my source distribution or my wheel of this package I get the following message.

> twine register dist/mycroft-1.1.0-py3-none-any.whl
Registering package to https://upload.pypi.org/legacy/
Enter your username: billmcn
Enter your password: 
Registering mycroft-1.1.0-py3-none-any.whl
HTTPError: 410 Client Error: Project pre-registration is no longer required or supported, so continue directly to uploading files. for url: https://upload.pypi.org/legacy/

This makes it look like the register step is unnecessary. However, when I try to upload I get this error.

> twine upload dist/*
Uploading distributions to https://upload.pypi.org/legacy/
Enter your username: billmcn
Enter your password: 
Uploading mycroft-1.1.0-py3-none-any.whl
[================================] 23132/23132 - 00:00:00
HTTPError: 403 Client Error: You are not allowed to upload to 'mycroft'. for url: https://upload.pypi.org/legacy/

I get similar errors when I use python setup.py register and python setup.py upload instead of twine.

Due diligence:

  • I have an account on PyPI.
  • The package name "mycroft" has not been claimed. (pip search mycroft returns nothing.)
  • I am using twine version 1.9.1 and setuptools version 33.1.1.post20170320.
  • I am confident that the setup.py in my project is correct. (I link to the github project above if anyone wants to take a look.)
  • I do not have a ~/.pypirc on my machine.
  • I have experimented with various ~/.pypirc configurations and command line arguments to twine to no avail. Details here.
  • I have read all the Python packaging, PyPI, twine documentation and relevant Stack Overflow issues I can find, but none of them have helped me figure this out.

Please help. I can't believe my good luck that someone hasn't snagged the name "mycroft" yet and I want to get this resolved before they do. :-)

@wpm
Copy link
Author

wpm commented Aug 3, 2017

Looks like there is an already existing Mycroft package.

I guess the bug is that neither pip install mycroft or the search button on https://pypi.python.org/pypi turned it up.

(Also, can I get that name? It looks like the existing Mycroft package has been abandoned.)

@jamadden jamadden added the PEP 541 Issues blocked on the implementation of PEP 541 label Aug 3, 2017
@Mr-Optimistic
Copy link

I made a .pypirc in my home directory
The contents were :
[server-login]
username:abc
password:xyz

Dint add repo

Worked for me

@brainwane
Copy link

I'm sorry for the wait.

We have archived this repository since it's about the legacy PyPI codebase. There's a new support ticket queue and I ask that, if you are still interested in this request, you re-open your issue there so we can follow up.

We're working on implementing PEP 541 with a new process -- you can subscribe to pypi/warehouse#1506 to follow our progress. Once we do that, we'll start working through all the requests for package transfers within https://github.com/pypa/pypi-support/ .

Until then, unfortunately, all I can advise you to do is wait. My apologies.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
PEP 541 Issues blocked on the implementation of PEP 541
Projects
None yet
Development

No branches or pull requests

4 participants