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

Switch the default to uploading using Warehouse #177

Merged
merged 1 commit into from
Jun 10, 2016

Conversation

dstufft
Copy link
Member

@dstufft dstufft commented Jun 5, 2016

This should be a better experience for people, might want to wait on merging this though until it gets some more people using it optionally.

@annaraven
Copy link
Contributor

Is PyPI being replaced by Warehouse (new name and site and everything?) Or is Warehouse going to be the new internals for PyPI and users won't care?

@dstufft
Copy link
Member Author

dstufft commented Jun 5, 2016

Warehouse is the name of the software for what will power PyPI 2.0, the site name is still going to be "PyPI" (unless Brett Cannon or someone else decides to push for a rename). It will use a new URL though, instead of pypi.python.org it will just be pypi.io (but there will be redirects where possible).

@dstufft
Copy link
Member Author

dstufft commented Jun 5, 2016

Oh, and as you might have guessed from this PR, uploading to the new code base uses a dedicated domain, upload.pypi.io, so that we can bypass the CDN for uploading.

@annaraven
Copy link
Contributor

So what does this mean for the pypi section in ~/.pypirc?

@dstufft
Copy link
Member Author

dstufft commented Jun 5, 2016

This PR will make twine default to Warehouse if that pypi section does not have an explicit repository: key. A future PR to Python will do the same there. People who have an explicit repository: section will need to update that themselves.

Of course, people can opt into this today by adding an explicit repository: section (see https://mail.python.org/pipermail/distutils-sig/2016-June/029083.html).

@annaraven
Copy link
Contributor

So they can start using warehouse now by adding the following to their .pypirc file and calling with -r warehouse ? Will the "/legacy/" part of the url go away in the future?

[warehouse]
repository:https://upload.pypi.io/legacy/
username:
password:

@dstufft
Copy link
Member Author

dstufft commented Jun 5, 2016

Yes that can start using it now by doing that, and no it won't go away-- the /legacy/ refers to the fact it's using the legacy upload API (versus the new one I plan on writing at some point).

@annaraven
Copy link
Contributor

and will it use the same username and password as their current pypi?

@annaraven
Copy link
Contributor

also, is there a warehouse version of "testpypi"?

@dstufft
Copy link
Member Author

dstufft commented Jun 5, 2016

Yes, Warehouse and Legacy PyPI share a database-- so they're quite literally just two different views over the same data.

  • pypi.io is the same as pypi.python.org.
  • test.pypi.io is the same as testpypi.python.org.

@sigmavirus24
Copy link
Member

Triggering a new merged build on Travis

@sigmavirus24 sigmavirus24 merged commit d814c19 into pypa:master Jun 10, 2016
@sigmavirus24
Copy link
Member

Thank you again @dstufft and @annaraven for pulling that information out of Donald. =D

@annaraven
Copy link
Contributor

You're quite welcome. I'm good at asking stupid questions. ;-)

annaraven added a commit to annaraven/python-packaging-user-guide that referenced this pull request Jun 10, 2016
Per Twine issue 177. pypa/twine#177 Also, corrected how to register, to clarify you must specify the file, not use glob. Per Twine issue 176. pypa/twine#176
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

Successfully merging this pull request may close these issues.

None yet

3 participants