[issue33345] Documentation for PowerShell instructions

Steve Piercy <w...@stevepiercy.com> added the comment: After reviewing PowerShell syntax, I found it is impractical to support in Pyramid's documentation. The discussion we had may be useful. https://github.com/Pylons/pyramid/issue

[issue33345] Documentation for PowerShell instructions

New submission from Steve Piercy <w...@stevepiercy.com>: Effective 2017-11-20, PowerShell is now the default command shell on Windows 10, and possibly other versions. Command Prompt (cmd.exe) is still present, just no longer the default. https://support.microsoft.com/en-us/help/4

[issue27285] Document the deprecation of pyvenv in favor of `python3 -m venv`

Steve Piercy added the comment: Thanks, Ned. This was my first hg patch. I'm learning. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue27285] Document the deprecation of pyvenv in favor of `python3 -m venv`

Steve Piercy added the comment: I've attached a patch for the buildbot error at [library/venv:353]. However, as noted in my [second bullet point](http://bugs.python.org/issue27285#msg269649): - I removed the file Doc/using/scripts.rst because it became obsolete. This caused warnings in Doc

[issue27285] Document the deprecation of pyvenv in favor of `python3 -m venv`

Steve Piercy added the comment: Thank you! -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27285> ___ ___ Python-bugs-list

[issue27285] Document the deprecation of pyvenv in favor of `python3 -m venv`

Steve Piercy added the comment: Patch attached for review. Notes: - I built the docs using Sphinx 1.4.1, whereas I think 1.3.3 is in use in production. If you upgrade, you will need to specify the language for syntax highlighting, else you will get hundreds of these error messages: /Users

[issue27285] Document the deprecation of pyvenv in favor of `python3 -m venv`

Steve Piercy added the comment: 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

[issue27285] Document the deprecation of pyvenv in favor of `python3 -m venv`

Steve Piercy added the comment: I'd like to take on this issue and submit a patch for consideration by 2016-06-26. Please let me know if anyone is working on it. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue27285] Document the deprecation of pyvenv in favor of `python3 -m venv`

Steve Piercy added the comment: One more. https://docs.python.org/3/library/venv.html Should that be updated for 3.5.1 as well as 3.6? -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue27285] Document the deprecation of pyvenv in favor of `python3 -m venv`

Steve Piercy added the comment: See also: https://github.com/pypa/python-packaging-user-guide/issues/242 -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue27285] Document the deprecation of pyvenv in favor of `python3 -m venv`

Steve Piercy added the comment: I forgot to include the specific URL to update: https://docs.python.org/3/installing/ There may be other places. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue27285] Deprecate pyvenv in favor of python3 -m venv

Steve Piercy added the comment: I saw the patch in 3.6, yet the discussion in issue #25154 called for deprecation in 3.5.1. Was deprecation of `pyvenv` supposed to be implemented in 3.5.1? I couldn't find any other relevant discussion, so apologies for jumping in uninformed

[issue27285] Deprecate pyvenv in favor of python3 -m venv

New submission from Steve Piercy: Per https://bugs.python.org/issue25154 `pyvenv` is deprecated in favor of `python3 -m venv`. The docs for Python 3.5+ need to be updated accordingly. -- assignee: docs@python components: Documentation messages: 268104 nosy: docs@python, stevepiercy