[issue14939] Usage documentation for pyvenv

2012-05-29 Thread Vinay Sajip
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment: The Using section has 4 sub-sections: one on the Python command line, + 3 on Python usage on Windows, Linux and OS X. I propose to add a fourth sub-section Additional Tools and Scripts (feel free to suggest an alternative title) and under

[issue14939] Usage documentation for pyvenv

2012-05-29 Thread Vinay Sajip
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment: Done in ace7c340d95d. -- resolution: - fixed stage: needs patch - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14939

[issue14939] Usage documentation for pyvenv

2012-05-28 Thread Nick Coghlan
New submission from Nick Coghlan ncogh...@gmail.com: Command line documentation for pyvenv must be provided under http://docs.python.org/dev/using/index.html before 3.3 is released. -- assignee: docs@python components: Documentation messages: 161815 nosy: docs@python, ncoghlan,

[issue14939] Usage documentation for pyvenv

2012-05-28 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: I would document it in library/venv, just like other tools are documented in the relevant module docs. I’m nonetheless +1 to listing all scripts installed by Python in the Setup and Usage docs, with links. -- nosy: +eric.araujo

[issue14939] Usage documentation for pyvenv

2012-05-28 Thread Nick Coghlan
Nick Coghlan ncogh...@gmail.com added the comment: No, we need to start using the Setup Usage docs *more*, not less. All tools with useful command line behaviour (especially those that are directly installed as scripts) should eventually be documented here. The fact this has historically

[issue14939] Usage documentation for pyvenv

2012-05-28 Thread Tshepang Lekhonkhobe
Changes by Tshepang Lekhonkhobe tshep...@gmail.com: -- nosy: +tshepang ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14939 ___ ___