-
Notifications
You must be signed in to change notification settings - Fork 441
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(docs): describe when the Python interpreter must be bundled
- Loading branch information
Showing
1 changed file
with
21 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,23 @@ | ||
|
||
.. include:: /common/craft-parts/python_plugin.rst | ||
:end-before: .. _python-details-begin: | ||
|
||
Dependencies | ||
------------ | ||
|
||
Whether the Python interpreter needs to be included in the snap depends on its | ||
``confinement``. Specifically: | ||
|
||
- Projects with ``strict`` or ``devmode`` confinement can safely use the base | ||
snap's interpreter, so they typically do **not** need to include Python. | ||
- Projects with ``classic`` confinement **cannot** use the base snap's | ||
interpreter, and thus must always bundle it (typically via ``stage-packages``). | ||
- In both cases, a specific/custom Python installation can always be included | ||
in the snap. This can be useful, for example, when using a different Python | ||
version or building an interpreter with custom flags. | ||
|
||
Snapcraft will prefer an included interpreter over the base's, even for projects | ||
with ``strict`` and ``devmode`` confinement. | ||
|
||
.. include:: /common/craft-parts/python_plugin.rst | ||
:start-after: .. _python-details-end: |