Skip to content
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

1.1.0 advertised on PyPi, but no distribution appears to be available #412

Closed
ViktorHaag opened this issue Apr 12, 2016 · 11 comments
Closed

Comments

@ViktorHaag
Copy link
Contributor

1.1.0 seems to be listed as available on PyPi, but with no associated distribution available.

If this is just a timing issue with uploading the package, I apologize for adding an issue that's effectively noise.

@ViktorHaag ViktorHaag changed the title 1.1.0 advertised on PyPi, but not distribution appears to be available 1.1.0 advertised on PyPi, but no distribution appears to be available Apr 12, 2016
@eofs
Copy link
Contributor

eofs commented Apr 13, 2016

I've the same problem, the distribution for 1.1.0 is not available:

DistributionNotFound: No distributions matching the version for oauthlib==1.1.0

#408

@Starefossen
Copy link

Starefossen commented Apr 28, 2016

@idan @thedrow are there anything I, or the community, can do to help with getting the lastes version published on PyPi?

@thedrow
Copy link
Collaborator

thedrow commented Apr 28, 2016

Travis must have failed to push the package. I'll retry and do it manually if it fails again.

@thedrow
Copy link
Collaborator

thedrow commented Apr 28, 2016

I'm getting HTTPError: 400 Client Error: This filename has previously been used, you should use a different version. when I try to upload the release both manually and in travis.
Any idea what is this all about?

@thedrow
Copy link
Collaborator

thedrow commented Apr 28, 2016

Ok done. I had to rename the source distribution for some reason.
@ViktorAtD2L @eofs @Starefossen Next time ping me directly with @thedrow on such issues or catch me on twitter or something.
I hope not to disregard these kind of problems in the future.

@thedrow thedrow closed this as completed Apr 28, 2016
@r4fek
Copy link
Contributor

r4fek commented Apr 28, 2016

@thedrow now it doesn't play well with Devpi.. Advertised version is 1.1.0, but package is called 1.1.0-1. Devpi is unable to install 1.1.0 then (it sees only 1.1.0-1). Maybe you could bump release version and upload it this time correctly?

@ViktorHaag
Copy link
Contributor Author

I believe that this is a security feature of PyPi: once a distribution is created, you can't alter its contents, so that no two package versions have the same name. However, I understood that if you registered a new package version without providing files, you could then manually attach files to the version: I may be incorrect in believing that.

@thedrow thedrow reopened this Apr 28, 2016
@thedrow
Copy link
Collaborator

thedrow commented Apr 28, 2016

@r4fek I'll re-release tomorrow.

@r4fek
Copy link
Contributor

r4fek commented Apr 28, 2016

Awesome!

@thedrow
Copy link
Collaborator

thedrow commented May 1, 2016

Done.
Please let me know if you find any problems.

@thedrow
Copy link
Collaborator

thedrow commented May 1, 2016

I just tested it and it's installed and upgraded just fine.

@thedrow thedrow closed this as completed May 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants