This release is a pre-release and may not be stable for production use.
datasette-remove-database
Remove a database from Datasette
Installation
Install this plugin in the same environment as Datasette.
datasette install datasette-remove-database
Usage
Users with the remove-database permission will see a new menu item on the database page that allows them to remove the database.
By default databases that are removed from Datasette will still be available on disk.
To also delete the file from disk, add this configuration:
plugins:
datasette-remove-database:
delete: true
Development
To set up this plugin locally, first checkout the code. Then create a new virtual environment:
cd datasette-remove-database
python -m venv venv
source venv/bin/activate
Now install the dependencies and test dependencies:
pip install -e '.[test]'
To run the tests:
python -m pytest
1 maintainer
Metadata
1 maintainer
Release files for datasette-remove-database 0.1a2
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_remove_database-0.1a2.tar.gz | 4.0 kB | With provenance | Details for datasette_remove_database-0.1a2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datasette_remove_database-0.1a2-py3-none-any.whl | Python 3 | none | any | Details for datasette_remove_database-0.1a2-py3-none-any.whl |
Total release size: 7.3 kB
Release files / datasette_remove_database-0.1a2.tar.gz
| Download URL | datasette_remove_database-0.1a2.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
926d1cce985253d5eee147081abbfa9ed0541e9c82140ef1ca40e3f370cfa0dd
|
|
BLAKE2b-256 checksum How to use checksums |
46fdddd8b1f64614a09456349ec5a30ef690b95ceff6bab13347196a7f7acba3
|
| 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 Nov 8, 2025.
Transparency logRelease files / datasette_remove_database-0.1a2-py3-none-any.whl
| Download URL | datasette_remove_database-0.1a2-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f4a0fec533c8c5557d9349f0b65b4a06f39c0041da46597321928007fc44c83
|
|
BLAKE2b-256 checksum How to use checksums |
70fe9726680293e411dc9fb1031bb5f65e095ff5f041ff77d19fad523b3c47a6
|
| 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 Nov 8, 2025.
Transparency logSecurity for datasette-remove-database 0.1a2
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
Both files in this release have been uploaded with provenance metadata.
Attestation for datasette_remove_database-0.1a2.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 Nov 8, 2025.
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.
