qlever 0.5.25__py3-none-any.whl → 0.5.26__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Potentially problematic release.
This version of qlever might be problematic. Click here for more details.
- {qlever-0.5.25.dist-info → qlever-0.5.26.dist-info}/METADATA +40 -29
- {qlever-0.5.25.dist-info → qlever-0.5.26.dist-info}/RECORD +6 -6
- {qlever-0.5.25.dist-info → qlever-0.5.26.dist-info}/WHEEL +0 -0
- {qlever-0.5.25.dist-info → qlever-0.5.26.dist-info}/entry_points.txt +0 -0
- {qlever-0.5.25.dist-info → qlever-0.5.26.dist-info}/licenses/LICENSE +0 -0
- {qlever-0.5.25.dist-info → qlever-0.5.26.dist-info}/top_level.txt +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: qlever
|
|
3
|
-
Version: 0.5.
|
|
3
|
+
Version: 0.5.26
|
|
4
4
|
Summary: Command-line tool for using the QLever graph database
|
|
5
5
|
Author-email: Hannah Bast <bast@cs.uni-freiburg.de>
|
|
6
6
|
License: Apache-2.0
|
|
@@ -21,37 +21,30 @@ Dynamic: license-file
|
|
|
21
21
|
|
|
22
22
|
# QLever
|
|
23
23
|
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
does, in particular, creating SPARQL endpoints for arbitrary RDF datasets. It
|
|
31
|
-
is supposed to be very easy to use and self-explanatory as you use it. In
|
|
32
|
-
particular, the tool provides context-sensitive autocompletion of all its
|
|
33
|
-
commands and options. If you use a container system (like Docker or Podman),
|
|
34
|
-
you don't even have to download any QLever code, but the script will download
|
|
35
|
-
the required image for you.
|
|
36
|
-
|
|
37
|
-
NOTE: There has been a major update on 24.03.2024, which changed some of the
|
|
38
|
-
Qleverfile variables and command-line options (all for the better, of course).
|
|
39
|
-
If you encounter any problems, please contact us by opening an issue on
|
|
40
|
-
https://github.com/ad-freiburg/qlever-control/issues.
|
|
24
|
+
This repository provides a self-documenting and easy-to-use command-line tool
|
|
25
|
+
for QLever (pronounced "Clever"), a graph database implementing the
|
|
26
|
+
[RDF](https://www.w3.org/TR/rdf11-concepts/) and
|
|
27
|
+
[SPARQL](https://www.w3.org/TR/sparql11-overview/) standards.
|
|
28
|
+
For a detailed description of what QLever is and what it can do, see
|
|
29
|
+
[here](https://github.com/ad-freiburg/qlever).
|
|
41
30
|
|
|
42
31
|
# Installation
|
|
43
32
|
|
|
44
|
-
Simply do `pip install qlever` and make sure that the directory where pip
|
|
33
|
+
Simply do `pip install qlever` and make sure that the directory where `pip`
|
|
45
34
|
installs the package is in your `PATH`. Typically, `pip` will warn you when
|
|
46
|
-
that is not the case and tell you what to do.
|
|
35
|
+
that is not the case and tell you what to do. If you encounter an "Externally
|
|
36
|
+
managed Environment" error, try `pipx` instead of `pip`.
|
|
37
|
+
|
|
38
|
+
Type `qlever` without arguments to check that the installation worked. When
|
|
39
|
+
using it for the first time, you will see a warning at the top with
|
|
40
|
+
instructions on how to enable autocompletion. Do it, it makes using `qlever`
|
|
41
|
+
so much easier (`pip` cannot do that for you automatically, sorry).
|
|
47
42
|
|
|
48
43
|
# Usage
|
|
49
44
|
|
|
50
45
|
Create an empty directory, with a name corresponding to the dataset you want to
|
|
51
46
|
work with. For the following example, take `olympics`. Go to that directory
|
|
52
|
-
and do the following.
|
|
53
|
-
activate autocompletion for all its commands and options (it's very easy, but
|
|
54
|
-
`pip` cannot do that automatically).
|
|
47
|
+
and do the following.
|
|
55
48
|
|
|
56
49
|
```
|
|
57
50
|
qlever setup-config olympics # Get Qleverfile (config file) for this dataset
|
|
@@ -78,16 +71,34 @@ qlever index --show
|
|
|
78
71
|
```
|
|
79
72
|
|
|
80
73
|
There are many more commands and options, see `qlever --help` for general help,
|
|
81
|
-
`qlever <command> --help` for help on a specific command, or just the
|
|
74
|
+
`qlever <command> --help` for help on a specific command, or just use the
|
|
82
75
|
autocompletion.
|
|
83
76
|
|
|
77
|
+
# Use on macOS and Windows
|
|
78
|
+
|
|
79
|
+
By default, `qlever` uses [QLever's official Docker
|
|
80
|
+
image](https://hub.docker.com/r/adfreiburg/qlever). In principle, that image
|
|
81
|
+
runs on Linux, macOS, and Windows. On Linux, Docker runs natively
|
|
82
|
+
and incurs only a relatively small overhead regarding performance and RAM
|
|
83
|
+
consumption. On macOS and Windows, Docker runs in a virtual machine, which
|
|
84
|
+
incurs a significant and sometimes unpredictable overhead. For example, `qlever
|
|
85
|
+
index` might abort prematurely (without a proper error message) because the
|
|
86
|
+
virtual machine runs out of RAM.
|
|
87
|
+
|
|
88
|
+
For optimal performance, compile QLever from source on your machine. For Linux,
|
|
89
|
+
this is relatively straightforward: just follow the `RUN` instructions in the
|
|
90
|
+
[Dockerfile](https://github.com/ad-freiburg/qlever/blob/master/Dockerfile). For
|
|
91
|
+
macOS, this is more complicated, see [this
|
|
92
|
+
workflow](https://github.com/ad-freiburg/qlever/blob/master/.github/workflows/macos.yml).
|
|
93
|
+
|
|
84
94
|
# Use with your own dataset
|
|
85
95
|
|
|
86
|
-
To use QLever with your own dataset, you
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
change it according to your needs (the variable names should be
|
|
90
|
-
Pick one for a dataset that is similar to yours and when in
|
|
96
|
+
To use QLever with your own dataset, you need a `Qleverfile`, like in the
|
|
97
|
+
example above. The easiest way to write a `Qleverfile` is to get one of the
|
|
98
|
+
existing ones (using `qlever setup-config ...` as explained above) and then
|
|
99
|
+
change it according to your needs (the variable names should be
|
|
100
|
+
self-explanatory). Pick one for a dataset that is similar to yours and when in
|
|
101
|
+
doubt, pick `olympics`.
|
|
91
102
|
|
|
92
103
|
# For developers
|
|
93
104
|
|
|
@@ -46,9 +46,9 @@ qlever/commands/system_info.py,sha256=I84EKgMO5J8pvsTDhkVKHzsRLtPajNg9KTQN5kWjqL
|
|
|
46
46
|
qlever/commands/ui.py,sha256=Kjv5FKN0pjMCpJS6otbrczs364x24FAnsJjtnc98mJQ,9811
|
|
47
47
|
qlever/commands/update_wikidata.py,sha256=1IkYqrgbIV2tJliEORhzv1rMjjipnxe-5FTLrKes1FA,23312
|
|
48
48
|
qlever/commands/warmup.py,sha256=kJHzS7HJo8pD2CphJuaXDj_CYP02YDo2DVM-pun3A80,1029
|
|
49
|
-
qlever-0.5.
|
|
50
|
-
qlever-0.5.
|
|
51
|
-
qlever-0.5.
|
|
52
|
-
qlever-0.5.
|
|
53
|
-
qlever-0.5.
|
|
54
|
-
qlever-0.5.
|
|
49
|
+
qlever-0.5.26.dist-info/licenses/LICENSE,sha256=xx0jnfkXJvxRnG63LTGOxlggYnIysveWIZ6H3PNdCrQ,11357
|
|
50
|
+
qlever-0.5.26.dist-info/METADATA,sha256=GS_dGYncRUVfYJvuV67nBTaMwvb8jQhf25j9nyg76kU,5151
|
|
51
|
+
qlever-0.5.26.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
|
|
52
|
+
qlever-0.5.26.dist-info/entry_points.txt,sha256=U_1U6SFIEZ-AnNlvk2nzcL0e4jnjEpuSbxYZ_E0XpEg,51
|
|
53
|
+
qlever-0.5.26.dist-info/top_level.txt,sha256=kd3zsYqiFd0--Czh5XTVkfEq6XR-XgRFW35X0v0GT-c,7
|
|
54
|
+
qlever-0.5.26.dist-info/RECORD,,
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|