This release is a pre-release and may not be stable for production use.
datasette-debug-gotham
A debugging utility for testing actor permissions/actions with DC Superheros (superman, Batman, Daily Planet, etc.)
It can be hard to test or debug Datasette plugins that use the new permissions system. This plugin offers a few builtin actors and a small widget for switching between actors:
Once you select an actor like "Clark Kent" or "Bruce Wayne", the page will refresh and Datasette will recognize the actor in request.actor. You can change actors however you like:
The pre-configured actors have some attributes you can use for debugging or "group permissions":
# https://github.com/datasette/datasette-debug-gotham/blob/main/datasette_debug_gotham/__init__.py#L8-L21
ACTORS = {
###### DAILY PLANET ######
"clark": {
"id": "clark",
"name": "Clark Kent",
"newsroom": "daily-planet",
"profile_picture_url": pfp("C", bg="blue"),
},
"lois": {
"id": "lois",
"name": "Lois Lane",
"newsroom": "daily-planet",
"profile_picture_url": pfp("L", bg="red"),
},
... # many more
}
Or access the actors with Python:
from dataseette_debug_gotham import ACTORS
print(ACTORS["clark"])
Personally I use this with uv for dynamic permissions testing:
uvx \
--from 'datasette>=1a' \
--with datasette-debug-gotham \
datasette \
--default-deny \
-s permissions.view-instance.newsroom daily-planet \
--memory
Here --default-deny means that by default everyone will see a Forbidden view-instance error when visiting dataset.
But, if you use the debug widget and select clark/lois/jimmy, since they have newsroom: daily-planet in their actor config, they will be able to see the instance!
And if you change to bruce/alfred/selina, who have newsroom: gotham-gazette, they will be blocked!
Metadata
Release files for datasette-debug-gotham 0.1.0a3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| datasette_debug_gotham-0.1.0a3.tar.gz | 12.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| datasette_debug_gotham-0.1.0a3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.8 kB
Release files / datasette_debug_gotham-0.1.0a3.tar.gz
| Download URL | datasette_debug_gotham-0.1.0a3.tar.gz |
|---|---|
| Size | 12.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db3e4ed3d526bc16db3cbae398a9a10ab2523e7790dc2614ddce1ef476b54a10
|
|
BLAKE2b-256 checksum How to use checksums |
29b61876d995bb9e17bcf3e52fff038c8bef3832da42710d975521c5c23d7a1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency logRelease files / datasette_debug_gotham-0.1.0a3-py3-none-any.whl
| Download URL | datasette_debug_gotham-0.1.0a3-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
420edd559af96c6b301e704a1fe7c23dc9f16a38f66105f6702bb908f3e36fbf
|
|
BLAKE2b-256 checksum How to use checksums |
5618f22428bd300191f400744d278e041bb8abb478c67df6f09b072572ba249f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 16, 2026.
Transparency log