-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Documentation rewrite (Q1 2021) #9474
Conversation
Oh, and you can probably see this in the RTD preview -- my rough plan for the hierarchy/structure is:
|
5805e74
to
a4557fe
Compare
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
a4557fe
to
2f9593f
Compare
2f9593f
to
93d35f5
Compare
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
@pypa/pip-committers this seems like it's gonna a big PR, so it'd be nice if someone could start reviewing this incrementally, since... There's a lot here and I don't know of any way to do this in smaller chunks. Ideas for breaking this up into smaller chunks are super welcome. :) |
In the Getting Started page, it’s probably better to
|
Or, if you don’t mind more conflicts, I can just propose them separately to the current documentation 🙂 |
pip supports loading credentials from a user's `.netrc` file. If no credentials | ||
are part of the URL, pip will attempt to get authentication credentials for the | ||
URL's hostname from the user's `.netrc` file. This behaviour comes from the | ||
underlying use of [`requests`][pypi-requests], which in turn delegates it to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, I never added the link. :)
This simplifies the Sphinx configuration and adds additional grouping and structure to the existing code as well.
Use eval-rst, for directives that don't support MyST yet.
76918a4
to
a339fb1
Compare
Ad. repeatable installs chapter: In my opinion it would be worth to add a note box saying that updating dependency in a "pip frozen" environment can be a pain, because requirements.txt file lacks information which dependency is top-level and which is not. And for such use cases pip-tools and other dependency managers are preferred. |
I've broken out #9693 from this PR, to make it easier to separate the "scaffolding changes" from the "content changes". I'm thinking of ways to make it possible for us to incrementally switch between these structures, but more on that in follow up PRs! :) |
Dumping this here, because I can't think of a better place ATM:
|
Hello! I am an automated bot and I have noticed that this pull request is not currently able to be merged. If you are able to either merge the |
``` | ||
|
||
A requirements file, containing pinned package versions can be generated using | ||
{ref}`pip freeze`. This would not only the top-level packages, but also all of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence lacks a predicate.
Closing this out, since this is being broken up into smaller chunks, as part of #9475. :) |
See #9475 for context and the overall idea here.
PS: If you're reviewing this, I'd say, either look at the PR preview or go commit-by-commit. Looking at the total diff will be painful.