oldest-supported-numpy
Meta-package that provides the oldest NumPy that supports a given Python version and platform. If wheels for the platform became available on PyPI only for a more recent NumPy version, then that NumPy version is specified.
Decision gist · record as of 2026-08-14
Yes, if you maintain a package with NumPy C extensions and want to avoid manual version pinning in pyproject.toml. The dormant maintenance status is not a concern because the package's role is static—it maintains a mapping that only needs updates when NumPy or Python versions change. Check that the pinned NumPy versions still match your platform and Python support before adopting it.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Intended only for build-time use in pyproject.toml; not a runtime package for application code.
- Requires Python >= 3.7.
- Low friction; single runtime dependency (numpy).
License · maintenance · safety
BSD (permissive) — BSD license is permissive; no restrictions on use or redistribution in your own projects.
last release 2023-12-21 (967 days) · last repo commit 2024-09-15 · 55 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 13,547,387 downloads/mo, #1,275 on PyPI
Alternatives
Verify before relying
# In pyproject.toml:
[build-system]
requires = ["wheel", "setuptools", "oldest-supported-numpy"]
# oldest-supported-numpy automatically installs the appropriate NumPy version
# for your Python version and platform during build.- Whether the NumPy version pinnings remain accurate for current Python releases beyond 3.7.
- Whether dormant status (no commits since 2024-09-15) will delay updates if NumPy or Python compatibility issues arise.
What it is and what it does
oldest-supported-numpy is a meta-package that solves a specific build-time problem: when you compile C extensions against NumPy, binaries built with older NumPy versions remain compatible with newer NumPy versions, but not vice versa. This package automatically selects and provides the oldest NumPy version that works with your target Python version and platform, eliminating the need to manually maintain a long list of version pins in your pyproject.toml.
You use it by adding it to your build-system requires list instead of manually pinning NumPy versions for each Python version. The package contains a static mapping of Python versions to the oldest compatible NumPy release (or the oldest with prebuilt wheels for your platform), and pip installs that NumPy version into your build environment automatically. This is purely a build-time convenience; your package can still require a newer NumPy at runtime if needed.
Use it for
- Building a NumPy-based C extension without manually maintaining version pins for each Python version.
- Ensuring compiled wheels remain forward-compatible with newer NumPy versions in user environments.
- Simplifying pyproject.toml for packages that depend on NumPy's C API but don't require recent NumPy features.
- Updating build requirements automatically as new Python versions are released, without editing pyproject.toml.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you maintain a package with NumPy C extensions and want to avoid manual version pinning in pyproject.toml.
The dormant maintenance status is not a concern because the package's role is static—it maintains a mapping that only needs updates when NumPy or Python versions change. Check that the pinned NumPy versions still match your platform and Python support before adopting it.
Install
oldest-supported-numpy on PyPI
Before you install
Low friction; single runtime dependency (numpy). Dormant maintenance status (last release 2023-12-21, no commits since 2024-09-15), but the package's role is narrow and stable—it maintains a static mapping of Python versions to NumPy versions rather than active feature development.
Intended only for build-time use in pyproject.toml; not a runtime package for application code. Requires Python >= 3.7.
License in practice
BSD license is permissive; no restrictions on use or redistribution in your own projects.
Quickstart
# In pyproject.toml:
[build-system]
requires = ["wheel", "setuptools", "oldest-supported-numpy"]
# oldest-supported-numpy automatically installs the appropriate NumPy version
# for your Python version and platform during build.Verify before relying
- Whether the NumPy version pinnings remain accurate for current Python releases beyond 3.7.
- Whether dormant status (no commits since 2024-09-15) will delay updates if NumPy or Python compatibility issues arise.
Package facts
| License | BSD permissive |
| Python support | Supports the current Python release >=3.7 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 1 packagenumpy |
| Maintenance | Dormant 967 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 13,547,387 / month, #1,275 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: oldest_supported_numpy-2023.12.21-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “numpy abi compatibility build”
- oldest-supported-numpyProvides the oldest version of NumPy compatible with a given Python…
- apache-tvm-ffiProvides a stable, minimal C ABI and FFI for machine learning systems…
- abi3auditabi3audit scans Python extension wheels and shared objects for…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also legacy-cgi · requirementslib · simplesat · pip-tools · versioningit · swig · scikit-build-core · bump · patchelf-wrapper · pkg-about