The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for bae-mem 0.3.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 | |
|---|---|---|---|---|
| bae_mem-0.3.0.tar.gz | 178.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bae_mem-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 437.6 kB
Release files / bae_mem-0.3.0.tar.gz
| Download URL | bae_mem-0.3.0.tar.gz |
|---|---|
| Size | 178.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c529c7ad31cdbd42f84be3fdf099323283c8eded6fea2cf6362833cad866dce
|
|
BLAKE2b-256 checksum How to use checksums |
bee8c245ab92a4439ce66c3c814d93ba598f360941cadf022b2be2e192d9cdc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.15
|
Release files / bae_mem-0.3.0-py3-none-any.whl
| Download URL | bae_mem-0.3.0-py3-none-any.whl |
|---|---|
| Size | 259.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fcdac1677a7e8ba9ec75ed828f10f1290fccf3603be6c6afec7f8b5e9c2b9b2e
|
|
BLAKE2b-256 checksum How to use checksums |
e7c10cf6d0e1fef5ca87c539ea82bb7a8eb5013a7f8ba720a277f5b455c8b833
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.15
|
Security for bae-mem 0.3.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.
