diff options
| author | Eli Schwartz <eschwartz@archlinux.org> | 2021-11-05 01:03:50 -0400 |
|---|---|---|
| committer | Eli Schwartz <eschwartz@archlinux.org> | 2022-02-22 22:22:16 -0500 |
| commit | 78945fb9832e989453fbabc471d45bb71805eca8 (patch) | |
| tree | 8a6dec38c143eb8645d59cc2ab01bc7a567f4f66 /docs/markdown/snippets | |
| parent | e8375d20a9aeb8c3b0ad58f299ded0e5e978b447 (diff) | |
| download | meson-78945fb9832e989453fbabc471d45bb71805eca8.zip meson-78945fb9832e989453fbabc471d45bb71805eca8.tar.gz meson-78945fb9832e989453fbabc471d45bb71805eca8.tar.bz2 | |
python module: add option to specify a python environment to install to
The default behavior of installing relative to prefix may be unexpected,
and is definitely wrong in many cases.
Give users control in order to specify that yes, they actually want to
install to a venv.
This is particularly useful for projects that use meson as a build
system for a python module, where *all* files shall be installed into
the python site-packages.
Diffstat (limited to 'docs/markdown/snippets')
| -rw-r--r-- | docs/markdown/snippets/python_module_env.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/markdown/snippets/python_module_env.md b/docs/markdown/snippets/python_module_env.md new file mode 100644 index 0000000..87a156d --- /dev/null +++ b/docs/markdown/snippets/python_module_env.md @@ -0,0 +1,9 @@ +## New option to choose python installation environment + +It is now possible to specify `-Dpython.install_env` and choose how python modules are installed. + +- `venv`: assume that a virtualenv is active and install to that +- `system`: install to the global site-packages of the selected interpreter + (the one that the venv module calls --system-site-packages) +- `prefix`: preserve existing behavior +- `auto`: autodetect whether to use venv or system |