pyrefly-numpy-stubs
NumPy type stubs with array shape information for Pyrefly.
This package is a PEP 561 stub-only distribution. It installs the
numpy-stubs stub package so Pyrefly can discover shape-aware stubs for the
runtime numpy package without replacing or shadowing NumPy itself.
The package is versioned in lockstep with Pyrefly and depends on the matching
pyrefly-shape-extensions package. Installing it also installs numpy, which
provides upstream modules used by these partial stubs. The numpy dependency is
unpinned, so projects can choose their own NumPy version.
Static checks use NumPy's installed stubs for APIs that this package re-exports:
python3 tensor-shapes/pyrefly-numpy-stubs/run_pyrefly.py
The runner uses ~/.tensor-shapes-venv by default. Set
$TENSOR_SHAPES_VENV to select another virtualenv, or pass --python with the
path to a virtualenv interpreter that has NumPy installed.
1 maintainer
Metadata
1 maintainer
Release files for pyrefly-numpy-stubs 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyrefly_numpy_stubs-1.4.0.tar.gz | 16.3 kB | With provenance | Details for pyrefly_numpy_stubs-1.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyrefly_numpy_stubs-1.4.0-py3-none-any.whl | Python 3 | none | any | Details for pyrefly_numpy_stubs-1.4.0-py3-none-any.whl |
Total release size: 35.0 kB
Release files / pyrefly_numpy_stubs-1.4.0.tar.gz
| Download URL | pyrefly_numpy_stubs-1.4.0.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b9238bcf8027a6e300febf1b421e6fab518f214695c88b1595c42cc37fa39f6b
|
|
BLAKE2b-256 checksum How to use checksums |
0c7df68a420d3a11ad74f8786f85224052146bc15f6ff67c627b99f62a38c2f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 15, 2026.
Transparency logRelease files / pyrefly_numpy_stubs-1.4.0-py3-none-any.whl
| Download URL | pyrefly_numpy_stubs-1.4.0-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a0c9ab467f1885cc5e17ea2994965c4c2bbd8af8a24443a09e5a2394cd8ab1ce
|
|
BLAKE2b-256 checksum How to use checksums |
a91153f5b24560b04aa2407d8c1b8b286d65ce55268666b83d4663a44fde18d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 15, 2026.
Transparency logSecurity for pyrefly-numpy-stubs 1.4.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pyrefly_numpy_stubs-1.4.0.tar.gz
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 Oct 15, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
