This project is similar to heapy (in the ‘guppy’ project), in its attempt to understand how memory has been allocated.
Currently, its main difference is that it splits the task of computing summary statistics, etc of memory consumption from the actual scanning of memory consumption. It does this, because I often want to figure out what is going on in my process, while my process is consuming huge amounts of memory (1GB, etc). It also allows dramatically simplifying the scanner, as I don’t allocate python objects while trying to analyze python object memory consumption.
It will likely grow to include a GUI for browsing the reference graph. For now it is mostly used in the python interpreter.
The name is simply a fun word (means Ash-wood Nymph).
1 maintainer
Metadata
1 maintainer
Release files for meliae 0.5.1
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 | |
|---|---|---|---|---|
| meliae-0.5.1.tar.gz | 205.5 kB | Without provenance | Details |
Release files / meliae-0.5.1.tar.gz
| Download URL | meliae-0.5.1.tar.gz |
|---|---|
| Size | 205.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cea42d693194fba32039f7136220da7ce93754b68e40de069b45258c15aa0668
|
|
BLAKE2b-256 checksum How to use checksums |
3dee62a9262225e1f093419cda015c3942392d4056ebfeec4c98a71a35c63fe2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.8.0 tqdm/4.19.5 CPython/3.6.9
|
Security for meliae 0.5.1
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.
