diff options
authorMichał Górny <>2017-05-10 15:28:41 +0200
committerMichał Górny <>2017-05-16 19:11:30 +0200
commit0fcdbe8b3c7335397fc43fbdf1cd1091ffc84097 (patch)
tree545dd5293195a6bce97808465b68eec84a0ffd0b /eclass/python-utils-r1.eclass
parentpython-utils-r1.eclass: Remove stray old doc bit (diff)
python-utils-r1.eclass: python_moduleinto, clarify relative path use
Clearly indicate that python_moduleinto can be safely called outside of the environment with Python interpreter established, and that a single call can set the correct relative path for multiple different implementations.
Diffstat (limited to 'eclass/python-utils-r1.eclass')
1 files changed, 6 insertions, 0 deletions
diff --git a/eclass/python-utils-r1.eclass b/eclass/python-utils-r1.eclass
index c46feb08449..c594cb46b5f 100644
--- a/eclass/python-utils-r1.eclass
+++ b/eclass/python-utils-r1.eclass
@@ -815,6 +815,12 @@ python_newscript() {
# When not set explicitly, the modules are installed to the top
# site-packages directory.
+# In the relative case, the exact path is determined directly
+# by each python_doscript/python_newscript function. Therefore,
+# python_moduleinto can be safely called before establishing the Python
+# interpreter and/or a single call can be used to set the path correctly
+# for multiple implementations, as can be seen in the following example.
# Example:
# src_install() {