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

Add instructions on how to use keyring #323

Merged
merged 2 commits into from
Mar 18, 2018

Conversation

theacodes
Copy link
Member

@codecov
Copy link

codecov bot commented Mar 18, 2018

Codecov Report

Merging #323 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #323   +/-   ##
=======================================
  Coverage   69.53%   69.53%           
=======================================
  Files          12       12           
  Lines         581      581           
  Branches       91       91           
=======================================
  Hits          404      404           
  Misses        150      150           
  Partials       27       27

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 7aeebc2...6eca1e5. Read the comment docs.

Copy link
Contributor

@brainwane brainwane left a comment

Choose a reason for hiding this comment

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

Great overall! A few small requests for improvement. Thank you!

README.rst Outdated
.. code-block:: console

$ keyring set https://upload.pypi.org/legacy/ your-username
$ python3 -m keyring set https://upload.pypi.org/legacy/ your-username
Copy link
Contributor

Choose a reason for hiding this comment

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

Please include the "or" between these two lines as you did above.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

* ``TWINE_USERNAME`` - the username to use for authentication to the repository
* ``TWINE_PASSWORD`` - the password to use for authentication to the repository
* ``TWINE_USERNAME`` - the username to use for authentication to the repository.
* ``TWINE_PASSWORD`` - the password to use for authentication to the repository.
* ``TWINE_REPOSITORY`` - the repository configuration, either defined as a
Copy link
Contributor

Choose a reason for hiding this comment

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

For parallelism, could you add the ending period to all the items in this list?

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.


$ keyring set https://test.pypi.org/legacy/ your-username
# or
$ python3 -m keyring set https://test.pypi.org/legacy/ your-username
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you find some way here to indicate that it'll ask you to input a password? And I have the same suggestion for line 116-117.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

README.rst Outdated
python3-dbus``. See `Keyring's installation instructions`_ for more details.

Once keyring is installed you can use the ``keyring`` program to set your
username and password for Twine.
Copy link
Contributor

Choose a reason for hiding this comment

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

Nitpick: I'd phrase this as:

"set your package index (repository) username and password for Twine to use"

Copy link
Member Author

Choose a reason for hiding this comment

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

Good call, I changed it even a bit more. LMK what you think.

@brainwane brainwane merged commit 1d4d940 into pypa:master Mar 18, 2018
@theacodes theacodes deleted the add-keyring-instructions branch March 18, 2018 21:21
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.

2 participants