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

[WIP] Docs refactor #562

Closed
wants to merge 13 commits into from
Closed

[WIP] Docs refactor #562

wants to merge 13 commits into from

Conversation

Ivoz
Copy link

@Ivoz Ivoz commented Feb 7, 2014

For pypa/packaging.python.org#5

Since virtualenv only consists of two/three commands at its heart (virtualenv, activate and deactivate) I thought a "quickstart" for these, without explaining what the heck they do and how to use them, would be somewhat unhelpful.

WIP -

  • look over options and make sure they're ok
  • add all necessary env vars (needed?)
  • refactor the explained options from the bottom of the userguide to reference? (e.g --extra-search-dir, --relocate)
  • Write a proper module documentation for virtualenv (in relation to its extensibility)?
  • Other sections could be removed / need major rewrite?

Request for comment, on the above

@qwcode
Copy link

qwcode commented Feb 7, 2014

oh, you did it. let me build it out and look later tonight....


.. _options:

Options
Copy link

Choose a reason for hiding this comment

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

the idea is for usage and options to be dynamic. see pip's usage page and it's use of extensions.

Copy link
Member

Choose a reason for hiding this comment

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

-1 virtualenv isn't a fast moving target when it comes to options, so I don't see a reason to not write the doc manually and add some proper prose to it

Copy link
Author

Choose a reason for hiding this comment

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

Is this really needed? Virtualenv isn't nearly as big as pip nor does it change as much. Plus pip needs to start using .. option:: directives itself!

Copy link

Choose a reason for hiding this comment

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

@jezdez, to be clear, this is for the "Reference Guide" portion, which I was intending to be a mostly "mechanical" rendering of the facts. The "User Guide" can be for more topical prose that covers the 80% cases.

see here for context : https://gist.github.com/qwcode/8431828
the "Pypa Template" idea is part of my plan on making the PUG links to Pypa docs appear more consistent and less jolting. I was planning on shuffling pip as well to this structure.

this may seem bit silly for virtualenv, since it's so small, but for pip and setuptools, I think it's significant.

@qwcode
Copy link

qwcode commented Feb 8, 2014

In order to see your local docs built using the RTD theme, see pip's conf.py
https://github.com/pypa/pip/blob/develop/docs/conf.py#L103
it helps to see it locally using the RTD theme
you'll need to install sphinx_rtd_theme

@@ -0,0 +1,256 @@
reference Guide
Copy link

Choose a reason for hiding this comment

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

capital "R"

@Ivoz Ivoz closed this Jun 14, 2014
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.

3 participants