This release is a pre-release and may not be stable for production use.
Metadata
Release files for xmemory 0.1a1
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 | |
|---|---|---|---|---|
| xmemory-0.1a1.tar.gz | 8.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xmemory-0.1a1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 17.6 kB
Release files / xmemory-0.1a1.tar.gz
| Download URL | xmemory-0.1a1.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b8fed82451407ffe8c4208603fa95ae9d5a0ed78ca7d6815fa541eddb83fdc8a
|
|
BLAKE2b-256 checksum How to use checksums |
40a4a9630047bfa2262d9a6423cba7c6efcda9fb459d69ef91053afa9d36322c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Release files / xmemory-0.1a1-py2.py3-none-any.whl
| Download URL | xmemory-0.1a1-py2.py3-none-any.whl |
|---|---|
| Size | 9.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
cc1bb11b2252a12c2f05c6f13351bdc2b6352810a8324dbf88edbfcf2b1fcc39
|
|
BLAKE2b-256 checksum How to use checksums |
51f4f66e1ea71b32f116bd0f921184ffd3b5b5babe4595cb9223e2f649be3da7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Security for xmemory 0.1a1
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.