1 |
Fix python_moduleinto doc to mention python_domodule rather than |
2 |
python_doscript (copy-paste error, probably). |
3 |
|
4 |
Signed-off-by: Michał Górny <mgorny@g.o> |
5 |
--- |
6 |
eclass/python-utils-r1.eclass | 8 ++++---- |
7 |
1 file changed, 4 insertions(+), 4 deletions(-) |
8 |
|
9 |
diff --git a/eclass/python-utils-r1.eclass b/eclass/python-utils-r1.eclass |
10 |
index 9eb068d3b13f..b3c249dfa694 100644 |
11 |
--- a/eclass/python-utils-r1.eclass |
12 |
+++ b/eclass/python-utils-r1.eclass |
13 |
@@ -805,10 +805,10 @@ python_newscript() { |
14 |
# site-packages directory. |
15 |
# |
16 |
# In the relative case, the exact path is determined directly |
17 |
-# by each python_doscript/python_newscript function. Therefore, |
18 |
-# python_moduleinto can be safely called before establishing the Python |
19 |
-# interpreter and/or a single call can be used to set the path correctly |
20 |
-# for multiple implementations, as can be seen in the following example. |
21 |
+# by each python_domodule invocation. Therefore, python_moduleinto |
22 |
+# can be safely called before establishing the Python interpreter and/or |
23 |
+# a single call can be used to set the path correctly for multiple |
24 |
+# implementations, as can be seen in the following example. |
25 |
# |
26 |
# Example: |
27 |
# @CODE |
28 |
-- |
29 |
2.35.1 |