Lerking/python-appimage
1
0
Fork 0
mirror of https://github.com/niess/python-appimage.git synced 2026-03-14 12:20:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

Relocate python wrapper

Browse Source
This commit is contained in:
Valentin Niess
2022-06-12 18:37:52 +02:00
parent 0097c4d942
commit 61fe3cedf9
7 changed files with 62 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/src/apps.md
View File

@@ -170,9 +170,9 @@ example, `$APPDIR` points to the AppImage mount point at runtime.
Python specific environment variables, the like `PYTHONPATH`. Depending on
your use case, this can be problematic.
The runtime isolation level can be changed by adding the `-s` and `-E`
The runtime isolation level can be changed by adding the `-E`, `-s` or `-I`
options, when invoking the runtime. For example,
`{{ python-executable }} -sE` starts a fully isolated Python instance.
`{{ python-executable }} -I` starts a fully isolated Python instance.
{% endraw %}
@@ -186,8 +186,8 @@ might rather refer to the initial AppImage [Packaging
Guide][APPIMAGE_PACKAGING], and use alternative tools like
[linuxdeploy][LINUXDEPLOY].
Yet, `python-appimage` can still be of use in more complex cases by extracting
its AppImages to an AppDir, as discussed in the [Advanced
However, `python-appimage` can still be of use in more complex cases by
extracting its AppImages to an AppDir, as discussed in the [Advanced
installation](index.md#advanced-installation) section. The extracted AppImages
contain a relocatable Python runtime, that can be used as a starting base for
building more complex AppImages.