You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would a contribution that quotes all these be of interest? Or as this is not necessarily required for installation of an extra should this not be added? If this is of interest, I have a branch on my fork with this done already that I can PR.
Describe the solution you'd like
Have the pip team decide if this is something they would like a docs contribution on or not. If so, then the contribution would be the following patch (or one that uses single quotes, but I was following the existing use of ")
python -m pip install SomePackage # latest version
to
python -m pip install "SomePackage"
is useful for helping avoid confusion — as you almost never see a package without a version qualifier on it being quoted I could see that it might even cause confusion.
What's the problem this feature will solve?
Some shells, like zsh, have glob qualifiers that will error if an extra is not quoted
Globbing can of course be turned off in these shells, but some users might not think of this right away.
At the moment all the extras in the pip install docs are unquoted:
pip/docs/html/cli/pip_install.rst
Lines 383 to 403 in 5e20a7b
Would a contribution that quotes all these be of interest? Or as this is not necessarily required for installation of an extra should this not be added? If this is of interest, I have a branch on my fork with this done already that I can PR.
Describe the solution you'd like
Have the
pip
team decide if this is something they would like a docs contribution on or not. If so, then the contribution would be the following patch (or one that uses single quotes, but I was following the existing use of"
)Alternative Solutions
Do nothing, as not quoting an extra works fine in shells like Bash that don't do globbing by default.
Additional context
This is a xref of pypa/packaging.python.org#1209
Code of Conduct
The text was updated successfully, but these errors were encountered: