https://github.com/astrofrog/oldest-supported-numpy-old

Meta-package providing the oldest supported Numpy for a given Python version and platform
https://github.com/astrofrog/oldest-supported-numpy-old

Last synced: 25 days ago
JSON representation

Meta-package providing the oldest supported Numpy for a given Python version and platform

• Host: GitHub
• URL: https://github.com/astrofrog/oldest-supported-numpy-old
• Owner: astrofrog
• License: bsd-2-clause
• Created: 2019-11-26T09:22:10.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2020-10-01T17:17:42.000Z (almost 6 years ago)
• Last Synced: 2026-05-24T07:42:17.037Z (about 2 months ago)
• Language: Python
• Size: 10.7 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.rst
  • License: LICENSE

Awesome Lists containing this project

README

          
.. image:: https://img.shields.io/pypi/v/oldest-supported-numpy

   :target: https://pypi.org/project/oldest-supported-numpy/

   :alt: PyPI

About

-----

This is a meta-package which can be used in ``pyproject.toml`` files to

automatically provide the oldest supported version of Numpy without having to

list them all. In other words::

    [build-system]

    requires = [

        "wheel",

        "setuptools",

        "numpy==1.13.3; python_version=='3.5',

        "numpy==1.13.3; python_version=='3.6',

        "numpy==1.14.5; python_version=='3.7',

        "numpy==1.17.3; python_version>='3.8'

    ]

can be replaced by::

    [build-system]

    requires = ["wheel", "setuptools", "oldest-supported-numpy"]

And as new Python versions are released, the ``pyproject.toml`` file does not

need to be updated.

Q&A

---

Why define the Numpy pinnings using install_requires in this repository?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Numpy version pinnings are defined inside the ``setup.cfg`` file as

``install_requires`` dependencies, rather than as build-time dependencies

inside ``pyproject.toml``. This is deliberate, since Numpy is not actually

required to build wheels of **oldest-supported-numpy**. What we need here

is to make sure that when **oldest-supported-numpy** is installed into

the build environment of a package using it, Numpy gets installed too

as a **runtime** dependency inside the build environment.

Another way to think about this is that since we only publish (universal)

wheels of **oldest-supported-numpy**, the wheel contains no ``pyproject.toml``,

``setup.cfg``, or ``setup.py`` code - it only contains metadata including

dependencies which get installed by pip when **oldest-supported-numpy** is

installed.

Can I use this if my package requires a recent version of Numpy?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In many cases, even though your package may require a version of

Numpy that is more recent than the pinned versions here, this

is often a runtime requirement, i.e. for running (rather than

building) your package. In many cases, unless you use recent

features of the Numpy C API, you will still be able to build your

package with an older version of Numpy and therefore you will still

be able to use **oldest-supported-numpy**. You can still impose a

more recent Numpy requirement in ``install_requires``

What about having a catchier name for this package?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The current name is not very catchy as package names go, but it

is very descriptive. This package is only meant to be used in

``pyproject.toml`` files for defining build-time dependencies,

so it's more important to have a descriptive than a catchy name!

What if I think that one of the pinnings is wrong or out of date?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Please feel free to `open an issue `_

or a pull request if you think something is wrong or could be improved!