smithy-aws-checksums
This package provides the checksum algorithms used by Smithy clients: CRC32,
CRC32C, CRC64NVME, XXHash64, XXHash3, XXHash128, and, through new(), SHA-1,
SHA-256, SHA-512, and MD5.
import smithy_aws_checksums
checksum = smithy_aws_checksums.new("CRC32C")
checksum.update(b"hello world")
checksum.digest()
Native acceleration
The CRC and XXHash algorithms are implemented in Rust and published as wheels for
common platforms. Where no wheel is available, the package installs as pure Python
and produces identical results, much more slowly. HAS_NATIVE_EXTENSION reports
which implementation is in use. CRC32 always uses zlib in pure Python, and the
SHA and MD5 algorithms always use hashlib.
Building
Wheels are built with maturin when cargo is on the
PATH, and as pure Python when no Rust toolchain is installed. If Rust is installed
but can't build the extension, for example because it's older than the
rust-version in Cargo.toml, the build fails with instructions instead of
silently falling back.
Set SMITHY_PYTHON_NATIVE_BUILD to never to build a pure-Python wheel, or to
always to require the native extension even when cargo isn't on the PATH.
Metadata
Release files for smithy-aws-checksums 0.0.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 |
|---|---|---|---|---|
| smithy_aws_checksums-0.0.0.tar.gz | 25.0 kB | Without provenance | Details for smithy_aws_checksums-0.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| smithy_aws_checksums-0.0.0-py3-none-any.whl | Python 3 | none | any | Details for smithy_aws_checksums-0.0.0-py3-none-any.whl |
Total release size: 48.6 kB
Release files / smithy_aws_checksums-0.0.0.tar.gz
| Download URL | smithy_aws_checksums-0.0.0.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46443e51d87cbd338a87c52dfdc46c0230b456b2d5c9a62213d04e9676675107
|
|
BLAKE2b-256 checksum How to use checksums |
b541416566b9f85fa94054df3465d96487a8ed7f0b4e785ccb56ba81d93a5040
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / smithy_aws_checksums-0.0.0-py3-none-any.whl
| Download URL | smithy_aws_checksums-0.0.0-py3-none-any.whl |
|---|---|
| Size | 23.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72d4cfe53a594f6af2f9e6bf17aa3a593069dca3aacd3332841b9dc4f9a9eaa4
|
|
BLAKE2b-256 checksum How to use checksums |
ee0a376de9ea42654e193d72260b44835ac4c6d76976f1c561866f127e8be9e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for smithy-aws-checksums 0.0.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.
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.