Skip to content

docs: clarify spaced version specifiers and shell quoting #2157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
harshitethic wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify spaced version specifiers and shell quoting #2157

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions source/tutorials/installing-packages.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -307,6 +307,16 @@ composed of a project name followed by an optional :term:`version specifier
found in the :ref:`Version specifier specification <version-specifiers>`.
Below are some examples.

Spaces within a requirement specifier are allowed, including around version
operators and commas. They can make manually maintained requirements easier to
read. For example, both ``pip ~= 23.1`` and
``resolvelib > 0.5, != 0.6.0`` are valid requirement specifiers.
In a requirements file, write them directly, one per line. When passing a
specifier containing spaces to ``pip install`` on the command line, quote
the entire requirement so the shell passes it as one argument (for example,
``python -m pip install "pip ~= 23.1"``).


To install the latest version of "SomeProject":

.. tab:: Unix/macOS
Expand Down
Loading