@@ -73,7 +73,7 @@ pip's tests are written using the :pypi:`pytest` test framework and
73
73
:mod: `unittest.mock `. :pypi: `nox ` is used to automate the setup and execution
74
74
of pip's tests.
75
75
76
- It is preferable to run the tests in parallel for better experience during development,
76
+ It is preferable to run the tests in parallel for a better experience during development,
77
77
since the tests can take a long time to finish when run sequentially.
78
78
79
79
To run tests:
@@ -104,6 +104,15 @@ can select tests using the various ways that pytest provides:
104
104
$ # Using keywords
105
105
$ nox -s test-3.10 -- -k "install and not wheel"
106
106
107
+ .. note ::
108
+
109
+ When running pip's tests with OS distribution Python versions, be aware that some
110
+ functional tests may fail due to potential patches introduced by the distribution.
111
+ For all tests to pass consider:
112
+
113
+ - Installing Python from `python.org `_ or compile from source
114
+ - Or, using `pyenv `_ to assist with source compilation
115
+
107
116
Running pip's entire test suite requires supported version control tools
108
117
(subversion, bazaar, git, and mercurial) to be installed. If you are missing
109
118
any of these VCS, those tests should be skipped automatically. You can also
@@ -114,6 +123,9 @@ explicitly tell pytest to skip those tests:
114
123
$ nox -s test-3.10 -- -k "not svn"
115
124
$ nox -s test-3.10 -- -k "not (svn or git)"
116
125
126
+ .. _python.org : https://www.python.org/downloads/
127
+ .. _pyenv : https://github.com/pyenv/pyenv
128
+
117
129
118
130
Running Linters
119
131
===============
0 commit comments