Drop Python 3.5 support
pytest no longer supports it, and our CI is broken because of it.
This commit is contained in:
10
README.rst
10
README.rst
@@ -149,16 +149,16 @@ where executing a high-scope fixture exactly once is important.
|
||||
Running tests in a Python subprocess
|
||||
------------------------------------
|
||||
|
||||
To instantiate a python3.5 subprocess and send tests to it, you may type::
|
||||
To instantiate a python3.9 subprocess and send tests to it, you may type::
|
||||
|
||||
pytest -d --tx popen//python=python3.5
|
||||
pytest -d --tx popen//python=python3.9
|
||||
|
||||
This will start a subprocess which is run with the ``python3.5``
|
||||
This will start a subprocess which is run with the ``python3.9``
|
||||
Python interpreter, found in your system binary lookup path.
|
||||
|
||||
If you prefix the --tx option value like this::
|
||||
|
||||
--tx 3*popen//python=python3.5
|
||||
--tx 3*popen//python=python3.9
|
||||
|
||||
then three subprocesses would be created and tests
|
||||
will be load-balanced across these three processes.
|
||||
@@ -371,7 +371,7 @@ You can also add default environments like this:
|
||||
.. code-block:: ini
|
||||
|
||||
[pytest]
|
||||
addopts = --tx ssh=myhost//python=python3.5 --tx ssh=myhost//python=python3.6
|
||||
addopts = --tx ssh=myhost//python=python3.9 --tx ssh=myhost//python=python3.6
|
||||
|
||||
and then just type::
|
||||
|
||||
|
||||
Reference in New Issue
Block a user