From e2a9aaf24b0e3bdd1f4e429ba7c032f1f03bb585 Mon Sep 17 00:00:00 2001 From: Bruno Oliveira Date: Mon, 14 Jan 2019 21:50:10 -0200 Subject: [PATCH] Add docs page about plans for dropping py27 and py34 Fix #4635 --- doc/en/contents.rst | 1 + doc/en/py27-py34-deprecation.rst | 22 ++++++++++++++++++++++ 2 files changed, 23 insertions(+) create mode 100644 doc/en/py27-py34-deprecation.rst diff --git a/doc/en/contents.rst b/doc/en/contents.rst index 9883eaa64..6bf97b453 100644 --- a/doc/en/contents.rst +++ b/doc/en/contents.rst @@ -41,6 +41,7 @@ Full pytest documentation backwards-compatibility deprecations + py27-py34-deprecation historical-notes license contributing diff --git a/doc/en/py27-py34-deprecation.rst b/doc/en/py27-py34-deprecation.rst new file mode 100644 index 000000000..97d9abf83 --- /dev/null +++ b/doc/en/py27-py34-deprecation.rst @@ -0,0 +1,22 @@ +Python 2.7 and 3.4 support plan +=============================== + +Python 2.7 EOL is fast approaching, with +upstream support `ending in 2020 `__. +Python 3.4's last release is scheduled for +`March 2019 `__. pytest is one of +the participating projects of the https://python3statement.org. + +We plan to drop support for Python 2.7 and 3.4 at the same time with the release of **pytest 5.0**, +scheduled to be released by **mid-2019**. Thanks to the `python_requires `__ ``setuptools`` option, +Python 2.7 and Python 3.4 users using a modern ``pip`` version +will install the last compatible pytest ``4.X`` version automatically even if ``5.0`` or later +are available on PyPI. + +During the period **from mid-2019 and 2020**, the pytest core team plans to make +bug-fix releases of the pytest ``4.X`` series by back-porting patches to the ``4.x-maintenance`` +branch. + +**After 2020**, the core team will no longer actively back port-patches, but the ``4.x-maintenance`` +branch will continue to exist so the community itself can contribute patches. The +core team will be happy to accept those patches and make new ``4.X`` releases **until mid-2020**.