mirror of
https://github.com/tiyn/wiki.git
synced 2026-08-25 17:51:37 +02:00
Compare commits
2 Commits
1ba082fb37
...
1075ec57e3
| Author | SHA1 | Date | |
|---|---|---|---|
| 1075ec57e3 | |||
| 75372a2220 |
@@ -9,7 +9,7 @@ for [LaTeX](/wiki/markup_language.md#latex) using the BibTeX format.
|
||||
Papis can be installed on most [Linux](/wiki/linux.md) distributions by acquiring the `papis`
|
||||
package.
|
||||
On some distributions there may be problems installing this from the official repository.
|
||||
Another option to install papis is to use [pip](/wiki/programming_language/python.md).
|
||||
Another option to install Papis is to use [pip](/wiki/programming_language/python.md).
|
||||
Alternatively it can be downloaded from [the GitHub page](https://github.com/papis/papis).
|
||||
|
||||
### Configuration
|
||||
@@ -17,7 +17,7 @@ Alternatively it can be downloaded from [the GitHub page](https://github.com/pap
|
||||
To use Papis a config file needs to be created.
|
||||
The path of the global config file is `~/.config/papis/config`.
|
||||
A minimal config can look like the following.
|
||||
Make sure to change the path of the papers directory.
|
||||
Make sure to change the path to the directory of the paper.
|
||||
|
||||
```txt
|
||||
[papers]
|
||||
@@ -128,8 +128,8 @@ Afterward the contents of the temporary database should be checked to be correct
|
||||
papis -l tmp-db edit
|
||||
```
|
||||
|
||||
Afterward the contents of the temporary library should be moved to the actualy directory where
|
||||
papis stores its entries.
|
||||
Afterward the contents of the temporary library should be moved to the actual directory where Papis
|
||||
stores its entries.
|
||||
The path for that can be found in the [config file](#configuration).
|
||||
|
||||
```sh
|
||||
@@ -140,6 +140,13 @@ Finally, the cache needs to be cleared
|
||||
[as described in the corresponding section](#clearing-the-cache) for Papis to display the new
|
||||
entries correctly.
|
||||
|
||||
Alternatively the BibTeX file can instantly be imported using the following command where `<file>`
|
||||
is a placeholder for the BibTeX file.
|
||||
|
||||
```sh
|
||||
papis bibtex read <file> import --all
|
||||
```
|
||||
|
||||
### Changing the Default Names of the Library
|
||||
|
||||
The changing of the default names is done by changing the [config file](#configuration).
|
||||
|
||||
@@ -29,8 +29,8 @@ to your `~/.profile`.
|
||||
You can then set and install your preferred version of python globally with
|
||||
`pyenv install <version>` and `pyenv global <version>`.
|
||||
|
||||
Analog to managing python versions, `pipenv` can manage
|
||||
[pip](/wiki/programming_language/python/uv.md) and package versions.
|
||||
Analog to managing python versions, `pipenv` can manage [pip](#pip) and
|
||||
[package versions](#package-management).
|
||||
A guide and description of the usage can be found on [gioele.io](https://gioele.io/pyenv-pipenv).
|
||||
|
||||
### Manual Installation
|
||||
@@ -95,7 +95,7 @@ itself every time.
|
||||
For general information about shebangs, executable scripts and the `chmod +x` command, refer to the
|
||||
corresponding section in the [Shell article](/wiki/linux/shell.md#shebangs).
|
||||
|
||||
For Python it is recommended to use the following shebang.
|
||||
For Python, it is recommended to use the following shebang.
|
||||
|
||||
```py
|
||||
#!/usr/bin/env python
|
||||
@@ -150,6 +150,7 @@ A more modern and arguably better approach is using
|
||||
#### venv Virtual Environments
|
||||
|
||||
[venv](https://docs.python.org/3/library/venv.html) can be used to create a virtual environment.
|
||||
It usually uses the standard [pip](#pip) manager for installing libraries.
|
||||
|
||||
```
|
||||
python -m venv <project-path>
|
||||
@@ -184,6 +185,61 @@ ln -s <local-venv> ~/.pyenv/versions/<venv-name>
|
||||
Using this setup the python version will automatically change when navigating into the project
|
||||
directory.
|
||||
|
||||
## Package Management
|
||||
|
||||
Python packages can be installed using package managers.
|
||||
For new projects it is generally recommended to use [uv](#uv), while [pip](#pip) is available by
|
||||
default in most Python installations and is supported by virtually all Python projects.
|
||||
|
||||
### pip
|
||||
|
||||
The `pip` package manager is the standard Python package manager and can be used to install, upgrade
|
||||
and remove Python packages.
|
||||
It is recommended to use `pip` inside a [virtual environment](#using-virtual-environments).
|
||||
|
||||
A package called `<package>` can be installed using
|
||||
|
||||
```sh
|
||||
pip install <package>
|
||||
```
|
||||
|
||||
To upgrade an already installed package run
|
||||
|
||||
```sh
|
||||
pip install --upgrade <package>
|
||||
```
|
||||
|
||||
Packages can be removed again using
|
||||
|
||||
```sh
|
||||
pip uninstall <package>
|
||||
```
|
||||
|
||||
To display all currently installed packages use
|
||||
|
||||
```sh
|
||||
pip list
|
||||
```
|
||||
|
||||
### uv
|
||||
|
||||
For new projects it is generally recommended to use [uv](/wiki/programming_language/python/uv.md),
|
||||
which provides a modern replacement for [pip](#pip), [venv](#venv-virtual-environments) and several
|
||||
other Python tools.
|
||||
The corresponding article describes installation, virtual environments, dependency management and
|
||||
further usage in detail.
|
||||
|
||||
## Modules
|
||||
|
||||
Python modules can be installed using package managers such as
|
||||
[pip](/wiki/programming_language/python/pip.md) or
|
||||
[uv](/wiki/programming_language/python/uv.md).
|
||||
|
||||
For most projects it is recommended to use a
|
||||
[virtual environment](#using-virtual-environments).
|
||||
For global installation the
|
||||
[system package managers](/wiki/linux/package_manager.md) can be used.
|
||||
|
||||
## Modules
|
||||
|
||||
Python modules can be installed using package managers such as
|
||||
@@ -222,10 +278,10 @@ Afterward all possible scikit-learn algorithms will run on the GPU instead of th
|
||||
### PyTorch
|
||||
|
||||
This section addresses the [PyTorch module](https://pytorch.org/).
|
||||
Pytorch is a machine learning resource which is often used for
|
||||
PyTorch is a machine learning resource which is often used for
|
||||
[neural networks](/wiki/neural_network.md).
|
||||
|
||||
#### Setup Pytorch with CUDA for GPU usage
|
||||
#### Setup PyTorch with CUDA for GPU usage
|
||||
|
||||
CUDA is also only available for Nvidia GPUs.
|
||||
For AMD GPUs refer to [the ROCm section](#setup-pytorch-with-rocm-for-gpu-usage).
|
||||
@@ -358,3 +414,31 @@ A simple example for the combination of two models (`model1` and `model2`) into
|
||||
output = model2(model1.output)
|
||||
combined_model = tf.keras.models.Model(inputs=model1.input, outputs=output)
|
||||
```
|
||||
|
||||
### matplotlib
|
||||
|
||||
The [matplotlib](https://matplotlib.org/) module is a plotting library for Python.
|
||||
|
||||
#### Qt Backend Not Found
|
||||
|
||||
When using [Wayland](/wiki/linux/wayland.md), matplotlib may fail with an error similar to the
|
||||
following.
|
||||
|
||||
```txt
|
||||
ImportError: Failed to import any of the following Qt binding modules:
|
||||
PyQt6, PySide6, PyQt5, PySide2
|
||||
```
|
||||
|
||||
This happens because matplotlib uses the Qt backend (`QtAgg`) for displaying interactive windows,
|
||||
but no Qt Python bindings are installed.
|
||||
|
||||
To fix the issue simply install `PyQt6` inside the current
|
||||
[Python environment](#using-virtual-environments).
|
||||
This may look like the following example where [uv](/wiki/programming_language/python/uv.md) is
|
||||
used but other environments such as [pip](#pip) can also be used.
|
||||
|
||||
```sh
|
||||
uv add PyQt6
|
||||
```
|
||||
|
||||
After installing `PyQt6`, interactive matplotlib windows should work correctly under Wayland.
|
||||
|
||||
Reference in New Issue
Block a user