This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author stevepiercy
Recipients berker.peksag, brett.cannon, docs@python, stevepiercy
Date 2016-06-29.06:37:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After looking into this issue, I need guidance to better define scope and intent, and how to go about submitting the changes. I found 81 occurrences of the term `pyvenv` in the documentation, either in reST files or docstrings, across about a dozen files.

1. Should I obliterate any mention of `pyvenv` (excluding HISTORY and whatsnew) or preserve a mention or two of it? For example, "`pyvenv` was the recommended tool for creating virtual environments for Python 3.3 and 3.4, and is deprecated in Python 3.6. Beginning in Python 3.5, the use of `venv` is recommended."

2. Is it preferred to submit one patch for all edited files, or one patch per edited file?

TIA for any guidance.
Date User Action Args
2016-06-29 06:37:57stevepiercysetrecipients: + stevepiercy, brett.cannon, docs@python, berker.peksag
2016-06-29 06:37:57stevepiercysetmessageid: <>
2016-06-29 06:37:57stevepiercylinkissue27285 messages
2016-06-29 06:37:57stevepiercycreate