How does one determine the minimum patch version of Python supporting a __future__ functionality?

Viewed 52

I am a maintainer for a Python library that is considering supporting PEP 604, now in Python3.10

Our library currently supports Python3.8+ and so we figure that the __future__ inbuilt library will allow us to make use of this. We do however want to be very explicit in the versions of Python we support.

Python3.8.0 was released at roughly the same time as PEP 604 was introduced, and it likely launched with a __future__ library that did not already have a working implementation of PEP 604, so this was probably added to Python__future__ in a patch release that came later.

What I would like to know is the following:

  1. Generally, are the features backported to __future__ added in tow with stability/security updates to the specified minor version of Python, or are the features offered by __future__ set at the date of initial release for a new minor Python version (ie: Python X.Y.0)?
  2. Is PEP 604 available in Python3.8.0 via the __future__ library? If not, when was it introduced to Python3.8's __future__?
  3. Is there somewhere in the body of Python documentation that details the exact point releases where new features are backported to minor releases of Python via __future__?
0 Answers
Related