To use
export BLITE_TRACING_ENABLED=1
from blite_tracing.trace import start_event, end_event, write_trace
start_event("event_name")
your_code_here
end_event("event_name")
write_trace()
It's just a one file codebase, very tine, just refer to trace.py for any details. Basically we just
write to json in the format that chorme://tracing undertands.
Metadata
Release files for blite-tracing 0.1.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 | Actions |
|---|---|---|---|---|
| blite_tracing-0.1.1.tar.gz | 40.8 kB | Without provenance | Details for blite_tracing-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| blite_tracing-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for blite_tracing-0.1.1-py3-none-any.whl |
Total release size: 43.5 kB
Release files / blite_tracing-0.1.1.tar.gz
| Download URL | blite_tracing-0.1.1.tar.gz |
|---|---|
| Size | 40.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59efa35c96d1f803d4d7c8ce9a39e5efbd5ce31180d31204e51e78a512bb098d
|
|
BLAKE2b-256 checksum How to use checksums |
862b03f1e8d84995bd69b5ba319ce9f3a1e070b504b3f74293a5570b800471db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.4
|
Release files / blite_tracing-0.1.1-py3-none-any.whl
| Download URL | blite_tracing-0.1.1-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09f09a07e23a6fae559b19cec0a5d2b055c01e7215554af49a1cc6c6dd4411ce
|
|
BLAKE2b-256 checksum How to use checksums |
1b44e23e8d2c066411b8071020bb5160b4c2fdba539c9a97019266d0a31a9143
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.4
|
Security for blite-tracing 0.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.