QLever
This repository provides a self-documenting and easy-to-use command-line tool for QLever (pronounced "Clever"), a graph database implementing the RDF and SPARQL standards. For a detailed description of what QLever is and what it can do, see here.
Documentation
View the latest documentation at https://docs.qlever.dev/quickstart.
Installation
There are native packages available for
On other platforms simply install the qlever command-line
python package using pipx/uv.
Note: QLever will be executed in a container which will come with a performance penalty.
Use with your own dataset
To use QLever with your own dataset, you need a Qleverfile, like in the
example above. The easiest way to write a Qleverfile is to get one of the
existing ones (using qlever setup-config ...) and then
change it according to your needs. Pick one for a dataset that is similar to
yours and when in doubt, pick olympics. A
reference of all options is available.
For developers
The (Python) code for the script is in the *.py files in src/qlever. The
preconfigured Qleverfiles are in src/qlever/Qleverfiles.
If you want to make changes to the script, or add new commands, do as follows:
git clone https://github.com/ad-freiburg/qlever-control
cd qlever-control
pip install -e ".[dev]"
# To also render index resource-usage plots, add the "plot" extra:
# pip install -e ".[dev,plot]"
Then you can use qlever just as if you had installed it via pip install qlever. Note that you don't have to rerun pip install -e ".[dev]" when you modify
any of the *.py files and not even when you add new commands in
src/qlever/commands. The executable created by pip simply links and refers
to the files in your working copy.
If you have bug fixes or new useful features or commands, please open a pull
request. If you have questions or suggestions, please open an issue. Files have
to be formatted and linted with ruff:
# manually
ruff format
ruff check
# runs automatically before every commit
pre-commit install
1 maintainer
Metadata
1 maintainer
Release files for qlever 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| qlever-0.6.0.tar.gz | 208.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qlever-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 467.2 kB
Release files / qlever-0.6.0.tar.gz
| Download URL | qlever-0.6.0.tar.gz |
|---|---|
| Size | 208.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bd3fb700016afeaad738ada4df5f056cacb2fdf7a68886969459a56dc449ca2
|
|
BLAKE2b-256 checksum How to use checksums |
3c2baf5aa7bf814d51b5a5670ae5489f95ecf28a49545b40c61c9382b891add8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency logRelease files / qlever-0.6.0-py3-none-any.whl
| Download URL | qlever-0.6.0-py3-none-any.whl |
|---|---|
| Size | 259.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
21e4b37aed32603e3d6067212f4edea1edebd5426665d86acdb9a34b8d5ad1c3
|
|
BLAKE2b-256 checksum How to use checksums |
48497998ee0f300101f93d33fcf438b64295489ba8f677e5b94dc2e0c539b7de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 13, 2026.
Transparency log
