Assorted debugging facilities.
Lock, RLock, Thread: wrappers for threading facilties; simply import from here instead of there
thread_dump, stack_dump: dump thread and stack state
@DEBUG: decorator to wrap functions in timing and value debuggers
@trace: decorator to report call and return from functions
@trace_caller: decorator to report caller of function
TracingObject: subclass of cs.obj.Proxy that reports attribute use
1 maintainer
Metadata
1 maintainer
Release files for cs-debug 20150116
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 |
|---|---|---|---|---|
| cs.debug-20150116.tar.gz | 4.7 kB | Without provenance | Details for cs.debug-20150116.tar.gz |
Release files / cs.debug-20150116.tar.gz
| Download URL | cs.debug-20150116.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee593c108e73d2a4b7726f64b082141493e0fa65a2cc3ec370865f7cbb0b29a2
|
|
BLAKE2b-256 checksum How to use checksums |
9f58cb5fd66d3cb33cb8d7a193368623c9a8811e98004c5adca6d30259691857
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cs-debug 20150116
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.
