Remove docs on Python 2.7 and 3.4 Support (#9957)
This extensive explanation is not need anymore because they are now unsupported for a long time. Instead add as short section on Python version compatibility in the backward compatibility docs.
This commit is contained in:
Tim Hoffmann
GitHub
parent
cc0fbbefa0
commit
5d28a58640
|
|
@ -77,3 +77,18 @@ Deprecation Roadmap
|
||||||
Features currently deprecated and removed in previous releases can be found in :ref:`deprecations`.
|
Features currently deprecated and removed in previous releases can be found in :ref:`deprecations`.
|
||||||
|
|
||||||
We track future deprecation and removal of features using milestones and the `deprecation <https://github.com/pytest-dev/pytest/issues?q=label%3A%22type%3A+deprecation%22>`_ and `removal <https://github.com/pytest-dev/pytest/labels/type%3A%20removal>`_ labels on GitHub.
|
We track future deprecation and removal of features using milestones and the `deprecation <https://github.com/pytest-dev/pytest/issues?q=label%3A%22type%3A+deprecation%22>`_ and `removal <https://github.com/pytest-dev/pytest/labels/type%3A%20removal>`_ labels on GitHub.
|
||||||
|
|
||||||
|
|
||||||
|
Python version support
|
||||||
|
======================
|
||||||
|
|
||||||
|
Released pytest versions support all Python versions that are actively maintained at the time of the release:
|
||||||
|
|
||||||
|
============== ===================
|
||||||
|
pytest version min. Python version
|
||||||
|
============== ===================
|
||||||
|
7.1+ 3.7+
|
||||||
|
6.2 - 7.0 3.6+
|
||||||
|
5.0 - 6.1 3.5+
|
||||||
|
3.3 - 4.6 2.7, 3.4+
|
||||||
|
============== ===================
|
||||||
|
|
|
||||||
|
|
@ -2618,7 +2618,8 @@ Important
|
||||||
|
|
||||||
This release is a Python3.5+ only release.
|
This release is a Python3.5+ only release.
|
||||||
|
|
||||||
For more details, see our :std:doc:`Python 2.7 and 3.4 support plan <py27-py34-deprecation>`.
|
For more details, see our `Python 2.7 and 3.4 support plan
|
||||||
|
<https://docs.pytest.org/en/7.0.x/py27-py34-deprecation.html>`_.
|
||||||
|
|
||||||
Removals
|
Removals
|
||||||
--------
|
--------
|
||||||
|
|
@ -2842,7 +2843,11 @@ Features
|
||||||
|
|
||||||
- :issue:`6870`: New ``Config.invocation_args`` attribute containing the unchanged arguments passed to ``pytest.main()``.
|
- :issue:`6870`: New ``Config.invocation_args`` attribute containing the unchanged arguments passed to ``pytest.main()``.
|
||||||
|
|
||||||
Remark: while this is technically a new feature and according to our :ref:`policy <what goes into 4.6.x releases>` it should not have been backported, we have opened an exception in this particular case because it fixes a serious interaction with ``pytest-xdist``, so it can also be considered a bugfix.
|
Remark: while this is technically a new feature and according to our
|
||||||
|
`policy <https://docs.pytest.org/en/7.0.x/py27-py34-deprecation.html#what-goes-into-4-6-x-releases>`_
|
||||||
|
it should not have been backported, we have opened an exception in this
|
||||||
|
particular case because it fixes a serious interaction with ``pytest-xdist``,
|
||||||
|
so it can also be considered a bugfix.
|
||||||
|
|
||||||
Trivial/Internal Changes
|
Trivial/Internal Changes
|
||||||
------------------------
|
------------------------
|
||||||
|
|
@ -3014,7 +3019,8 @@ Important
|
||||||
|
|
||||||
The ``4.6.X`` series will be the last series to support **Python 2 and Python 3.4**.
|
The ``4.6.X`` series will be the last series to support **Python 2 and Python 3.4**.
|
||||||
|
|
||||||
For more details, see our :std:doc:`Python 2.7 and 3.4 support plan <py27-py34-deprecation>`.
|
For more details, see our `Python 2.7 and 3.4 support plan
|
||||||
|
<https://docs.pytest.org/en/7.0.x/py27-py34-deprecation.html>`_.
|
||||||
|
|
||||||
|
|
||||||
Features
|
Features
|
||||||
|
|
|
||||||
|
|
@ -85,7 +85,6 @@ Further topics
|
||||||
|
|
||||||
backwards-compatibility
|
backwards-compatibility
|
||||||
deprecations
|
deprecations
|
||||||
py27-py34-deprecation
|
|
||||||
|
|
||||||
contributing
|
contributing
|
||||||
development_guide
|
development_guide
|
||||||
|
|
|
||||||
|
|
@ -1,99 +0,0 @@
|
||||||
Python 2.7 and 3.4 support
|
|
||||||
==========================
|
|
||||||
|
|
||||||
It is demanding on the maintainers of an open source project to support many Python versions, as
|
|
||||||
there's extra cost of keeping code compatible between all versions, while holding back on
|
|
||||||
features only made possible on newer Python versions.
|
|
||||||
|
|
||||||
In case of Python 2 and 3, the difference between the languages makes it even more prominent,
|
|
||||||
because many new Python 3 features cannot be used in a Python 2/3 compatible code base.
|
|
||||||
|
|
||||||
Python 2.7 EOL has been reached :pep:`in 2020 <0373#maintenance-releases>`, with
|
|
||||||
the last release made in April, 2020.
|
|
||||||
|
|
||||||
Python 3.4 EOL has been reached :pep:`in 2019 <0429#release-schedule>`, with the last release made in March, 2019.
|
|
||||||
|
|
||||||
For those reasons, in Jun 2019 it was decided that **pytest 4.6** series will be the last to support Python 2.7 and 3.4.
|
|
||||||
|
|
||||||
What this means for general users
|
|
||||||
---------------------------------
|
|
||||||
|
|
||||||
Thanks to the `python_requires`_ setuptools option,
|
|
||||||
Python 2.7 and Python 3.4 users using a modern pip version
|
|
||||||
will install the last pytest 4.6.X version automatically even if 5.0 or later versions
|
|
||||||
are available on PyPI.
|
|
||||||
|
|
||||||
Users should ensure they are using the latest pip and setuptools versions for this to work.
|
|
||||||
|
|
||||||
Maintenance of 4.6.X versions
|
|
||||||
-----------------------------
|
|
||||||
|
|
||||||
Until January 2020, the pytest core team ported many bug-fixes from the main release into the
|
|
||||||
``4.6.x`` branch, with several 4.6.X releases being made along the year.
|
|
||||||
|
|
||||||
From now on, the core team will **no longer actively backport patches**, but the ``4.6.x``
|
|
||||||
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.6.X releases **until mid-2020**
|
|
||||||
(but consider that date as a ballpark, after that date the team might still decide to make new releases
|
|
||||||
for critical bugs).
|
|
||||||
|
|
||||||
.. _`python_requires`: https://packaging.python.org/guides/distributing-packages-using-setuptools/#python-requires
|
|
||||||
|
|
||||||
Technical aspects
|
|
||||||
~~~~~~~~~~~~~~~~~
|
|
||||||
|
|
||||||
(This section is a transcript from :issue:`5275`).
|
|
||||||
|
|
||||||
In this section we describe the technical aspects of the Python 2.7 and 3.4 support plan.
|
|
||||||
|
|
||||||
.. _what goes into 4.6.x releases:
|
|
||||||
|
|
||||||
What goes into 4.6.X releases
|
|
||||||
+++++++++++++++++++++++++++++
|
|
||||||
|
|
||||||
New 4.6.X releases will contain bug fixes only.
|
|
||||||
|
|
||||||
When will 4.6.X releases happen
|
|
||||||
+++++++++++++++++++++++++++++++
|
|
||||||
|
|
||||||
New 4.6.X releases will happen after we have a few bugs in place to release, or if a few weeks have
|
|
||||||
passed (say a single bug has been fixed a month after the latest 4.6.X release).
|
|
||||||
|
|
||||||
No hard rules here, just ballpark.
|
|
||||||
|
|
||||||
Who will handle applying bug fixes
|
|
||||||
++++++++++++++++++++++++++++++++++
|
|
||||||
|
|
||||||
We core maintainers expect that people still using Python 2.7/3.4 and being affected by
|
|
||||||
bugs to step up and provide patches and/or port bug fixes from the active branches.
|
|
||||||
|
|
||||||
We will be happy to guide users interested in doing so, so please don't hesitate to ask.
|
|
||||||
|
|
||||||
**Backporting changes into 4.6**
|
|
||||||
|
|
||||||
Please follow these instructions:
|
|
||||||
|
|
||||||
#. ``git fetch --all --prune``
|
|
||||||
|
|
||||||
#. ``git checkout origin/4.6.x -b backport-XXXX`` # use the PR number here
|
|
||||||
|
|
||||||
#. Locate the merge commit on the PR, in the *merged* message, for example:
|
|
||||||
|
|
||||||
nicoddemus merged commit 0f8b462 into pytest-dev:features
|
|
||||||
|
|
||||||
#. ``git cherry-pick -m1 REVISION`` # use the revision you found above (``0f8b462``).
|
|
||||||
|
|
||||||
#. Open a PR targeting ``4.6.x``:
|
|
||||||
|
|
||||||
* Prefix the message with ``[4.6]`` so it is an obvious backport
|
|
||||||
* Delete the PR body, it usually contains a duplicate commit message.
|
|
||||||
|
|
||||||
**Providing new PRs to 4.6**
|
|
||||||
|
|
||||||
Fresh pull requests to ``4.6.x`` will be accepted provided that
|
|
||||||
the equivalent code in the active branches does not contain that bug (for example, a bug is specific
|
|
||||||
to Python 2 only).
|
|
||||||
|
|
||||||
Bug fixes that also happen in the mainstream version should be first fixed
|
|
||||||
there, and then backported as per instructions above.
|
|
||||||
Loading…
Reference in New Issue