Typesafety is a tool for writing type-checked code in Python. In languages like C++, Java, etc., this is a language-level feature, but Python has no such feature. With the advent of annotations it is however possible to write code with type notations. Typesafety is a means to enforce that those notations are valid.
2 maintainers
Metadata
2 maintainers
Release files for typesafety 2.1.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 | |
|---|---|---|---|---|
| typesafety-2.1.2.tar.gz | 12.7 kB | Without provenance | Details |
Release files / typesafety-2.1.2.tar.gz
| Download URL | typesafety-2.1.2.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05d2ce340cc9a087857c710d354e803d32276b092b9ba3445dbca957978a81cb
|
|
BLAKE2b-256 checksum How to use checksums |
0fb2561f510ab1888d13b069df5edb38bf0f399a5ef83aeed898787230786e3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for typesafety 2.1.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.
