@@ -24,9 +24,9 @@ julia> using Pkg # for julia ≥ 0.7
24
24
julia> Pkg. add (" PyCall" )
25
25
```
26
26
27
- Your python installation must be able to call Julia. If your installer
28
- does not add the Julia binary directory to your ` PATH ` , you will have to
29
- add it. _ An alias will not work._
27
+ Your python installation must be able to call command line program
28
+ ` julia ` . If your installer does not add the Julia binary directory to
29
+ your ` PATH ` , you will have to add it. _ An alias will not work._
30
30
31
31
Then finally you have to install PyJulia.
32
32
@@ -51,7 +51,7 @@ install PyJulia directly from GitHub:
51
51
$ python3 -m pip install --user ' https://github.com/JuliaPy/pyjulia/archive/master.zip#egg=julia'
52
52
```
53
53
54
- You may clone it directly to your home directory.
54
+ You may clone it directly to (say) your home directory.
55
55
56
56
``` console
57
57
$ git clone https://github.com/JuliaPy/pyjulia
@@ -97,7 +97,7 @@ Other variants of Python import syntax also work:
97
97
98
98
``` pycon
99
99
>>> import julia.Base
100
- >>> from julia.Base import LinAlg # import a submodule
100
+ >>> from julia.Base import Enums # import a submodule
101
101
>>> from julia.Base import sin # import a function from a module
102
102
```
103
103
@@ -293,7 +293,7 @@ example, the Julia method `sum!` can be called in PyJulia using
293
293
There was a major overhaul in the module loading system between Julia
294
294
0.6 and 1.0. As a result,
295
295
[ the hack] ( https://github.com/JuliaPy/pyjulia/tree/master/julia/fake-julia )
296
- supporting the PyJulia to load PyCall.
296
+ supporting the PyJulia to load PyCall stopped working .
297
297
298
298
To understand the issue, you need to understand a bit of details in
299
299
PyCall implementation. PyCall uses Julia's precompilation mechanism
@@ -304,8 +304,8 @@ layout varies across Python versions. Currently, this is determined
304
304
while precompiling PyJulia and cannot be changed at run-time.
305
305
Consequently, PyCall only works if it loads the same libpython in
306
306
Julia and Python. This is why PyJulia has to be imported in a Python
307
- executable dynamically linked to libpython when using the same PyCall
308
- precompilation cache.
307
+ executable dynamically linked to libpython, if it shares the same
308
+ PyCall precompilation cache.
309
309
310
310
The aforementioned hack worked by monkey-patching Julia's
311
311
precompilation mechanism to emit the precompilation cache file to
0 commit comments