| 1 |
Clearly indicate that python_moduleinto can be safely called outside |
| 2 |
of the environment with Python interpreter established, and that |
| 3 |
a single call can set the correct relative path for multiple different |
| 4 |
implementations. |
| 5 |
--- |
| 6 |
eclass/python-utils-r1.eclass | 6 ++++++ |
| 7 |
1 file changed, 6 insertions(+) |
| 8 |
|
| 9 |
diff --git a/eclass/python-utils-r1.eclass b/eclass/python-utils-r1.eclass |
| 10 |
index c46feb08449b..c594cb46b5f3 100644 |
| 11 |
--- a/eclass/python-utils-r1.eclass |
| 12 |
+++ b/eclass/python-utils-r1.eclass |
| 13 |
@@ -815,6 +815,12 @@ python_newscript() { |
| 14 |
# When not set explicitly, the modules are installed to the top |
| 15 |
# site-packages directory. |
| 16 |
# |
| 17 |
+# In the relative case, the exact path is determined directly |
| 18 |
+# by each python_doscript/python_newscript function. Therefore, |
| 19 |
+# python_moduleinto can be safely called before establishing the Python |
| 20 |
+# interpreter and/or a single call can be used to set the path correctly |
| 21 |
+# for multiple implementations, as can be seen in the following example. |
| 22 |
+# |
| 23 |
# Example: |
| 24 |
# @CODE |
| 25 |
# src_install() { |
| 26 |
-- |
| 27 |
2.13.0 |
Archives