If it does not match, it checks the next oldest version until it finds one that matches. When pip finds a package, it selects the most recent version possible, then checks python_requires. The point of python_requires is to fill the appropriate slot in the metadata. In general, never set an upper limit for python_requires.Never drop a version from your CI without also changing python_requires. If it fails, it tries the next oldest version until it finds one that matches. Pip tries to install the latest package, but checks python_requires.All packages in Scikit-HEP are required to add python_requires to setup.cfg or setup.py, or the equivalent setting for other PEP 517 build systems.

All packages in Scikit-HEP must support the Python versions listed in NEP 29.

In light of this plan, the Scikit-HEP developers have adopted the following guidelines for the Scikit-HEP packages.

The maintainers of Matplotlib, scikit-learn, IPython, Jupyter, yt, SciPy, NumPy, and scikit-image have come together and agreed on a plan for Python and NumPy version support called NEP 29.

Most recent version of python