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 code overview to docs #296

Merged
merged 2 commits into from
Feb 10, 2018
Merged

add code overview to docs #296

merged 2 commits into from
Feb 10, 2018

Conversation

lgh2
Copy link
Contributor

@lgh2 lgh2 commented Jan 31, 2018

This adds a brief overview of twine's architecture to the documentation. Please let me know if there are any additions or changes.

@codecov
Copy link

codecov bot commented Jan 31, 2018

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #296   +/-   ##
=======================================
  Coverage   67.42%   67.42%           
=======================================
  Files          12       12           
  Lines         574      574           
  Branches       91       91           
=======================================
  Hits          387      387           
  Misses        162      162           
  Partials       25       25

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 3e47035...14a5fce. Read the comment docs.

docs/index.rst Outdated
--------

Twine is a command-line tool for interacting with PyPI securely over HTTPS. Its
command line arguments are parsed in ``twine/twine/cli.py``. Currently, twine
Copy link
Member

Choose a reason for hiding this comment

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

Would you be willing to share the reasoning around specifying the path as "twine/twine"? I think most people will be viewing those files as just "twine/cli.py" or "twine/commands/register.py"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My reasoning for specifying the path as twine/twine is that is what the path is, including the twine directory that gets cloned from GitHub. If it's confusing to people, I can specify them as twine/cli.py.

Copy link
Member

Choose a reason for hiding this comment

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

I see what you mean now. I think it's more common to do the following:

git clone https://github.com/pypa/twine
cd twine
# edit twine/cli.py

I think the custom that I've seen tends to refer to things from the root of the repository. But that certainly isn't the only way to work on projects and maybe it's better to be explicit that we are talking about working that way?

@sigmavirus24
Copy link
Member

It seems there's a conflict in this pull request with your other pull request. Would you be willing to resolve those conflicts?

@lgh2
Copy link
Contributor Author

lgh2 commented Feb 8, 2018

Of course! I will push an updated branch.

@lgh2
Copy link
Contributor Author

lgh2 commented Feb 9, 2018

Hi @sigmavirus24 -- I have resolved the conflict. Please let me know if there is anything else you would like changes on.

@sigmavirus24
Copy link
Member

This is fantastic! Thanks @lgh2 👍

@sigmavirus24 sigmavirus24 merged commit fa11a12 into pypa:master Feb 10, 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.

2 participants