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

better "register" guidance and pypi.org migration advice #320

Merged
merged 6 commits into from
Mar 15, 2018

Conversation

brainwane
Copy link
Contributor

Address part of #11 and #311 by removing the pypi.org default for register, and improving command-line usage for register. Also improve style and provide better guidance in the README and in other usage help for register and upload, including suggesting users use Test PyPI before uploading distributions to pypi.org.

Once we get the usage wording down I'll also update the README in this PR to reflect the new usage text for upload and register.

Key line to review: https://github.com/pypa/twine/compare/pypi-migration-register?expand=1#diff-2190788b5d7d5b86131d0daf63dac4d1R72 in which I remove the default of pypi for the register command.

@codecov
Copy link

codecov bot commented Mar 14, 2018

Codecov Report

Merging #320 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #320   +/-   ##
=======================================
  Coverage   68.51%   68.51%           
=======================================
  Files          12       12           
  Lines         578      578           
  Branches       91       91           
=======================================
  Hits          396      396           
  Misses        157      157           
  Partials       25       25
Impacted Files Coverage Δ
twine/commands/upload.py 61.9% <ø> (ø) ⬆️
twine/commands/register.py 0% <ø> (ø) ⬆️
twine/utils.py 85.14% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7f86514...3bc3507. Read the comment docs.

@brainwane
Copy link
Contributor Author

cc @mauritsvanrees & @mplanchard in case you can review & advise.

@mauritsvanrees
Copy link
Contributor

LGTM. It makes things clearer.

It does not look like this requires changes in zest.releaser.

Also, by default zest.releaser does not use the register command anymore, unless you explicitly have an option in your ~/.pypirc or setup.cfg:

[zest.releaser]
register = yes

@mplanchard
Copy link

This looks good to me, too!

Copy link
Member

@di di left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Member

@jaraco jaraco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I didn't see anything objectionable, but did see many valuable changes.

@brainwane brainwane force-pushed the pypi-migration-register branch from f1d4f3b to d15277e Compare March 15, 2018 21:01
@brainwane brainwane force-pushed the pypi-migration-register branch from d15277e to a578fd9 Compare March 15, 2018 21:37
@brainwane brainwane changed the title WIP better "register" guidance and pypi.org migration advice better "register" guidance and pypi.org migration advice Mar 15, 2018
@brainwane
Copy link
Contributor Author

I think codecov is just broken right now. Disregarding it and merging.

@brainwane brainwane merged commit 5199edb into master Mar 15, 2018
@brainwane brainwane deleted the pypi-migration-register branch March 15, 2018 21:53
@brainwane brainwane mentioned this pull request Mar 16, 2018
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.

5 participants