Roundup Robot added the comment:
New changeset 31debd0dc0dc by Senthil Kumaran in branch '3.5':
Issue26017 - Suggest enclosing command args in double quotes when using
characters which get interpreted by shell.
https://hg.python.org/cpython/rev/31debd0dc0dc
New changeset 18ae23b69e08 by
Roundup Robot added the comment:
New changeset 668827be66d6 by Senthil Kumaran in branch '2.7':
Issue26017 - Suggest enclosing command args in double quotes when using
characters which get interpreted by shell.
https://hg.python.org/cpython/rev/668827be66d6
--
Senthil Kumaran added the comment:
Thanks for the review/comment Ezio. Agree with your suggestion and made the
change accordingly.
--
assignee: docs@python -> orsenthil
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
versions: +Python 2.7, Python 3.5, Python
Ezio Melotti added the comment:
I think it's enough to add a note that says that if the argument contains >
(and possibly other) special characters, then it needs to be quoted.
Examples that use > should also be quoted, but not the others one.
--
nosy: +ezio.melotti
Senthil Kumaran added the comment:
Here is the patch with the changes suggested by Brett.
Having created this patch, I had second thoughts on this change. Folks who use
pip often, usually use it without any quotes, like `pip install requests`, `pip
install CherryPy`. Pinned down versions are
New submission from Brett Cannon:
If you look at https://docs.python.org/3/installing/index.html it lists two
commands:
python -m pip install SomePackage==1.0.4# specific version
python -m pip install 'SomePackage>=1.0.4' # minimum version
If you notice that beyond the change from `==`
Zachary Ware added the comment:
I'd also suggest using double quotes ("); single quotes don't work on Windows.
C:\>echo 'test>=test'
C:\>dir /b test*
test'
C:\>type "test'"
'test
--
nosy: +zach.ware
___
Python tracker