You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ version number is returned by `PythonPlot.version`.
56
56
57
57
Compared to the PyPlot.jl package, there are a few differences in the API.
58
58
59
-
* To avoid type piracy, the functions `show`, `close`, `step`, and `fill` are renamed to `pltshow`, `pltclose`, `pltstep`, and `pltfill`, respectively. (You can also access them as `PythonPlot.show` etcetera.)
59
+
* To avoid type piracy, the functions `show`, `close`, `step`, and `fill` are renamed to `plotshow`, `plotclose`, `plotstep`, and `plotfill`, respectively. (You can also access them as `PythonPlot.show` etcetera.)
60
60
* The `matplotlibl.pyplot` module is exported as `pyplot` rather than as `plt`.
61
61
* The PythonCall package performs many fewer automatic conversions from Python types to Julia types (in comparison to PyCall). If you need to convert Matplotlib return values to native Julia objects, you'll need to do `using PythonCall` and call its `pyconvert(T, o)` or other conversion functions.
62
62
@@ -104,7 +104,7 @@ function (`plot` etc.) is evaluated.
104
104
However, if you use PythonPlot from a Julia script that is run non-interactively
105
105
(e.g. `julia myscript.jl`), then Matplotlib is executed in
0 commit comments