PyShp-stubs
Overview
- This library is simply to indicate to type checkers that type hints should be included from PyShp's
single file module ("shapefile.py"), even e.g. when being run with
mypy --ignore-missing-imports. - This is a minimal library. As a wheel it solely consists of an empty
py.typedmarker file in a dir "shapefile-stubs". It contains no actual stubs (as they're not needed, the type hints are in the main library) - It is intended to be installed (into "Lib\site-packages") alongside the main PyShp repo (
pip install Pyshp[stubs]). - The main PyShp repo (from version 3 onwards) contains inline type hints, but is currently a single file module ("shapefile.py").
- PEP 561 states ""The single-file module should be refactored into a package". We respectfully disagree.
- If
py.typedis installed alongside "shapefile.py" in"Lib\site-packages", all packages installed in that (virtual) Python env will be typechecked by mypy, whether they contain type info or not Nominal type stubs for PyShp.
Description
PyShp 3 is statically typed. PyShp has historically been a single file library (shapefile.py).
According to PEP 561, and the spec in order to add a py.typed marker file (without indicating to type checkers that every package the user has installed adajacent to PyShp should also be type checked, regardless of whether all such packages support that or not), "The single-file module should be refactored into a package".
Myself and several other project contributers are reluctant to give up the single-file module (shapefile.py). We quite like it.
The purpose of this package is purely to indicate to type-checkers that PyShp is typed. It just so happens to be primarily typed in-line in the main library, from which the stubs in shapefile.pyi are largely automatically generated by MyPy's stubgen.
Metadata
Release files for pyshp-stubs 0.0.2
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 |
|---|---|---|---|---|
| pyshp_stubs-0.0.2.tar.gz | 2.1 kB | Without provenance | Details for pyshp_stubs-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyshp_stubs-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for pyshp_stubs-0.0.2-py3-none-any.whl |
Total release size: 4.2 kB
Release files / pyshp_stubs-0.0.2.tar.gz
| Download URL | pyshp_stubs-0.0.2.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7164069eb81ba647dbb9db2dced56c050a0a0eb2e198e3750e2affce6444af2
|
|
BLAKE2b-256 checksum How to use checksums |
f8622905bd466efd8e79c36ff2a3455c5c04ac66348d410b37acd6f9bcd1defd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / pyshp_stubs-0.0.2-py3-none-any.whl
| Download URL | pyshp_stubs-0.0.2-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e49ffef12ae2b0830c67871ffd2d550bffd986b7c4e2d779e0005ba4ddef09f9
|
|
BLAKE2b-256 checksum How to use checksums |
07dcbefa5124fbf524603caed4b2a092fea113fa4e326da06e1acb4dba257197
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for pyshp-stubs 0.0.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.