numpy-typing-compat
NumPy version information that type-checkers understand
Overview
This package provides version-specific boolean constants that allow library authors to
write NumPy-version-dependent static type annotations. Similar to how you might use
if sys.version_info >= (3, 12): for Python version checks, numpy-typing-compat
enables static type-checkers to understand which NumPy version is being used and apply
appropriate type annotations.
Use Case
This package is particularly useful for libraries that need to support multiple NumPy
versions, for example because they follow
SPEC 0. However, there may have been
changes in NumPy that affect type annotations. For instance, the numpy.exceptions
module was introduced in NumPy 1.25, and contains the exceptions that were previously in
the global numpy namespace. In NumPy 2.0, these exceptions were removed from the
global namespace. So if you support <1.25 and also >=2.0, you will need to
conditionally import these exceptions to ensure compatibility across versions.
from numpy_typing_compat import NUMPY_GE_1_25
if NUMPY_GE_1_25:
from numpy.exceptions import AxisError
else:
from numpy import AxisError
Type checkers like mypy, pyright, and basedpyright understand these patterns and will apply the correct type annotations based on the installed NumPy version.
Installation
pip install numpy-typing-compat
The package automatically selects the appropriate version constants based on your
installed NumPy version. It does so by requiring a specific version of NumPy in its
pyproject.toml file, so that your package manager will install the correct version of
numpy-typing-compat that matches the NumPy version you have installed.
For example, if you have numpy==2.1.3 pinned in your pyproject.toml, and you run
uv add numpy-typing-compat, it will install numpy-typing-compat==2.1.*. That
specific version has NUMPY_GE_2_1 = True, and NUMPY_GE_2_2 = False set.
Note that numpy-typing-compat does not import numpy, and instead relies on the
package manager to install the correct version of numpy-typing-compat that matches the
installed NumPy version.
Reference
Array API
Additionally, the package provides a numpy_typing_compat.array_api namespace that's a
re-export of the numpy.array_api module on numpy < 2.0, or the main numpy module
on numpy >= 2.0. Note that the numpy.array_api module was introduced in
numpy >= 1.23, so it isn't available in numpy-typing-compat==1.22.*.
numpy.long
NumPy 2.0 introduced the new long and ulong scalar types, which are not available in
numpy < 2.0, and instead went by the names int_ and uint (which in numpy >= 2.0
are aliases for intp and uintp).
If you need to support both NumPy versions, you can use the long and ulong types
from numpy_typing_compat, which on numpy < 2.0 are aliases for np.int_ and
np.uint, and on numpy >= 2.0 are re-exports of np.long and np.ulong.
numpy.dtypes.StringDType
In NumPy 2.0, the numpy.dtypes.StringDType was introduced, but it wasn't until
NumPy 2.1 that it was also available in the numpy stubs. The
numpy_typing_compat.StringDType is a re-export of numpy.dtypes.StringDType on
numpy >= 2.1, and an alias of np.dtype[Never] on numpy < 2.1. This allows type
checkers to also accept StringDType as a valid type on numpy == 2.0.*.
Version constants
The following low-level boolean version constants are available:
| Constant | True when |
|---|---|
NUMPY_GE_1_22 |
numpy >= 1.22 |
NUMPY_GE_1_23 |
numpy >= 1.23 |
NUMPY_GE_1_25 |
numpy >= 1.25 |
NUMPY_GE_2_0 |
numpy >= 2.0 |
NUMPY_GE_2_1 |
numpy >= 2.1 |
NUMPY_GE_2_2 |
numpy >= 2.2 |
NUMPY_GE_2_3 |
numpy >= 2.3 |
Each constant is typed as Literal[True] or Literal[False] depending on your NumPy
version, allowing type checkers to perform accurate type narrowing.
2 maintainers
Release files for numpy-typing-compat 2.3.20250726
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| numpy_typing_compat-2.3.20250726.tar.gz | 3.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| numpy_typing_compat-2.3.20250726-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.3 kB
Release files / numpy_typing_compat-2.3.20250726.tar.gz
| Download URL | numpy_typing_compat-2.3.20250726.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffa89ab34e5f13549f84b9fd10be1d9873971055e6df305c9c9d4a88f10665a8
|
|
BLAKE2b-256 checksum How to use checksums |
f7651b9914c6edb875e36b24496ab63fd507a5ea1c2c45ddb11fe91ad554ec1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 26, 2025.
Transparency logRelease files / numpy_typing_compat-2.3.20250726-py3-none-any.whl
| Download URL | numpy_typing_compat-2.3.20250726-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
def439bdd78ece8893619515d2c6f856b1acf749ed10e26a4b76f5e3d87a312e
|
|
BLAKE2b-256 checksum How to use checksums |
d2778f52c7537dbe6982c1bb8c7c875ed1d6dc6470875e0742ebf922dc451080
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 26, 2025.
Transparency log
