datasette-pretty-traces
Prettier formatting for ?_trace=1 traces
Installation
Install this plugin in the same environment as Datasette.
datasette install datasette-pretty-traces
Usage
Once installed, run Datasette using --setting trace_debug 1:
datasette fixtures.db --setting trace_debug 1
Then navigate to any page and add ?_trace= to the URL:
http://localhost:8001/?_trace=1
The plugin will scroll you down the page to the visualized trace information.
Demo
You can try out the demo here:
- /?_trace=1 tracing the homepage
- /github/commits?_trace=1 tracing a table page
Screenshot
Development
To set up this plugin locally, checkout the code and run the tests with uv run pytest:
cd datasette-pretty-traces
uv run pytest
To try your development version of plugin run it like this:
uv run datasette fixtures.db --setting trace_debug 1
1 maintainer
Metadata
1 maintainer
Release files for datasette-pretty-traces 0.7
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 |
|---|---|---|---|---|
| datasette_pretty_traces-0.7.tar.gz | 11.5 kB | With provenance | Details for datasette_pretty_traces-0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datasette_pretty_traces-0.7-py3-none-any.whl | Python 3 | none | any | Details for datasette_pretty_traces-0.7-py3-none-any.whl |
Total release size: 23.2 kB
Release files / datasette_pretty_traces-0.7.tar.gz
| Download URL | datasette_pretty_traces-0.7.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
922c89a8239fb45661464f1de492c9be685170acd152ba4000e4867637ebfec5
|
|
BLAKE2b-256 checksum How to use checksums |
09645da99f369fb6ef3f3d84f034364acc0e8c73100e82ed103601cc87c15c27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 8, 2026.
Transparency logRelease files / datasette_pretty_traces-0.7-py3-none-any.whl
| Download URL | datasette_pretty_traces-0.7-py3-none-any.whl |
|---|---|
| Size | 11.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a7ffcc12d83d3e844f5275fdd30ebe7fae93a91100a9aa9c6cb61383c0ec4d7
|
|
BLAKE2b-256 checksum How to use checksums |
6f44b035a6752ea1105df77589e6a04f4b885590857cbe6b0dfab204248c4bd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 8, 2026.
Transparency logSecurity for datasette-pretty-traces 0.7
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for datasette_pretty_traces-0.7.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 8, 2026.
Transparency logA 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.
