diff options
| author | Adam Johnson <me@adamj.eu> | 2019-12-18 09:42:41 +0000 |
|---|---|---|
| committer | Carlton Gibson <carlton.gibson@noumenal.es> | 2019-12-18 10:43:36 +0100 |
| commit | a334ae5d1e9ff8b8dcfd1cb67fa0903930446980 (patch) | |
| tree | ab863bc7ae35bf0a95fcf4c705b285cf93ede2e6 /docs | |
| parent | f21c132cd4a5d2656f30b3bd9e7b035e39fe4966 (diff) | |
[3.0.x] Updated Pytest example in upgrade documentation.
Pytest changed their recommended entrypoint to 'pytest' in version 3.0.0 in 2016 : https://docs.pytest.org/en/latest/changelog.html#id1009. Also link the name since this is the only reference in the Django documentation at current.
Backport of ef3baf966d73c71480198d6194fa277ef7daa87d from master
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/howto/upgrade-version.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/howto/upgrade-version.txt b/docs/howto/upgrade-version.txt index a7ff10e710..9ce0be2b16 100644 --- a/docs/howto/upgrade-version.txt +++ b/docs/howto/upgrade-version.txt @@ -68,11 +68,11 @@ environment variable. For example, to show warnings while running tests: If you're not using the Django test runner, you may need to also ensure that any console output is not captured which would hide deprecation warnings. For -example, if you use `py.test`: +example, if you use `pytest <https://pytest.org/>`__: .. code-block:: console - $ PYTHONWARNINGS=always py.test tests --capture=no + $ PYTHONWARNINGS=always pytest tests --capture=no Resolve any deprecation warnings with your current version of Django before continuing the upgrade process. |