@@ -14,7 +14,7 @@ Installation
14
14
** Note:** If you are using Python installed with Ubuntu or ` conda ` ,
15
15
PyJulia may not work with Julia ≥ 0.7. For workarounds, see
16
16
[ Troubleshooting] ( #troubleshooting ) below. Same caution applies to
17
- other Debian-based and possibly other GNU/Linux distributions.
17
+ any Debian-based and possibly other GNU/Linux distributions.
18
18
19
19
You will need to install PyCall in your existing Julia installation
20
20
@@ -30,7 +30,7 @@ your `PATH`, you will have to add it. _An alias will not work._
30
30
Then finally you have to install PyJulia.
31
31
32
32
** Note:** If you are not familiar with ` pip ` and have some troubles
33
- with the following installation steps, we recommend to go through
33
+ with the following installation steps, we recommend going through the
34
34
[ Tutorials in Python Packaging User Guide] ( https://packaging.python.org/tutorials/ ) .
35
35
36
36
To get released versions you can use:
@@ -73,8 +73,8 @@ See [Testing](#testing) below for how to run tests.
73
73
Usage
74
74
-----
75
75
76
- PyJulia provides a high-level interface which assumes a "normal"
77
- setup (e.g., ` julia ` is in your ` PATH ` ) and a low-level interface
76
+ PyJulia provides a high-level interface which assumes a "normal" setup
77
+ (e.g., ` julia ` program is in your ` PATH ` ) and a low-level interface
78
78
which can be used in a customized setup.
79
79
80
80
### High-level interface
@@ -161,7 +161,7 @@ In [2]: %%julia
161
161
### Virtual environments
162
162
163
163
PyJulia can be used in Python virtual environments created by
164
- ` virtualenv ` , ` venv ` , and any tools wrapping them such as ` pipenv `
164
+ ` virtualenv ` , ` venv ` , and any tools wrapping them such as ` pipenv ` ,
165
165
provided that Python executable used in such environments are linked
166
166
to identical libpython used by PyCall. If this is not the case,
167
167
initializing PyJulia (e.g., ` import julia.Main ` ) prints an informative
@@ -200,8 +200,8 @@ $ ldd /usr/bin/python
200
200
in Linux where ` /usr/bin/python ` should be replaced with the path to
201
201
your ` python ` command (use ` which python ` to find it out). In macOS,
202
202
use ` otool -L ` instead of ` ldd ` . If it does not print the path to
203
- libpython like ` /usr/lib/libpython3.7m.so.1.0 ` in above, you need to
204
- use one of the workaround below.
203
+ libpython like ` /usr/lib/libpython3.7m.so.1.0 ` in above example , you
204
+ need to use one of the workaround below.
205
205
206
206
The easiest workaround is to use the ` python-jl ` command bundled in
207
207
PyJulia. This can be used instead of normal ` python ` command for
0 commit comments