From 8919dea6c822c3eb7020364898d6fd73250119c5 Mon Sep 17 00:00:00 2001 From: Robin Date: Mon, 19 Mar 2018 14:50:04 +0000 Subject: [PATCH] Update py34 to py36 Since py34 is no longer supported --- source/developers/development_testing.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/developers/development_testing.markdown b/source/developers/development_testing.markdown index 14dcf03c577..a4f462690dd 100644 --- a/source/developers/development_testing.markdown +++ b/source/developers/development_testing.markdown @@ -16,7 +16,7 @@ $ tox ``` **Important:** Run `tox` before you create your pull request to avoid annoying fixes. -Running Tox will run unit tests against the locally available Pythons, as well as validate the code and document style using `pycodestyle`, `pydocstyle` and `pylint`. You can run tests on only one tox target -- just use `-e` to select an environment. For example, `tox -e lint` runs the linters only, and `tox -e py34` runs unit tests only on Python 3.4. +Running Tox will run unit tests against the locally available Pythons, as well as validate the code and document style using `pycodestyle`, `pydocstyle` and `pylint`. You can run tests on only one tox target -- just use `-e` to select an environment. For example, `tox -e lint` runs the linters only, and `tox -e py36` runs unit tests only on Python 3.6. Tox uses virtual environments under the hood to create isolated testing environments. The tox virtual environments will get out-of-date when requirements change, causing test errors. Run `tox -r` to tell Tox to recreate the virtual environments.