[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/issues/3260 -- ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33345> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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/4027690/windows-powershell-is-replacing-command-prompt Current instructions for installing and configuring Python on Windows reference only Command Prompt. There may be other places. https://docs.python.org/3/using/windows.html#configuring-python FYI, we're in the process of updating our documentation for Pyramid where we have both PowerShell and Command Prompt. At some point in the future, we may drop the latter. https://github.com/Pylons/pyramid/issues/3260 Let me know what y'all think is the best way to proceed, even if that is no action. -- assignee: docs@python components: Documentation messages: 315690 nosy: docs@python, stevepiercy priority: normal severity: normal status: open title: Documentation for PowerShell instructions type: enhancement versions: Python 3.6, Python 3.7, Python 3.8 ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33345> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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/whatsnew/3.3.rst and Doc/whatsnew/3.4.rst which reference the obsolete file. I couldn't find a policy that addresses what to do in this situation, so I left it to the council of elders to provide me with their sage guidance. I'll submit a patch as soon as I know which path to follow. -- Added file: http://bugs.python.org/file43681/pyvenv-to-venv.update-susp-ignored.csv.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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/stevepiercy/projects/cpython/Doc/distutils/examples.rst:250: WARNING: Could not lex literal_block as "python3". Highlighting skipped. I made my changes accordingly, as they are backward compatible to Sphinx 1.3.3 and will be one fewer thing to update in future releases. - I removed the file Doc/using/scripts.rst because it became obsolete. This caused warnings in Doc/whatsnew/3.3.rst and Doc/whatsnew/3.4.rst which reference the obsolete file. - I updated a lot of links to https://packaging.python.org/ and others to save a redirect and to get link checking to pass. - I replaced confusing colloquialisms of "env", "venv", and "virtualenv" with "virtual environment" as appropriate. This clarifies that a virtual environment is the thing created, whereas `venv`, `pyvenv`, and `virtualenv` are modules/scripts/commands that create a virtual environment, or that "env" is the name of a directory. - Minor grammar, punctuation, and reST fixes. -- hgrepos: +346 keywords: +patch Added file: http://bugs.python.org/file43598/pyvenv-to-venv.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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. 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. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 priority: normal severity: normal status: open title: Deprecate pyvenv in favor of python3 -m venv type: enhancement versions: Python 3.5, Python 3.6 ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27285> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
