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: docs/src/faq.md
-11Lines changed: 0 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -18,17 +18,6 @@ Some rules if you are writing multithreaded code:
18
18
19
19
Related issues: [#201](https://github.com/JuliaPy/PythonCall.jl/issues/201), [#202](https://github.com/JuliaPy/PythonCall.jl/issues/202)
20
20
21
-
## Does it work on Apple silicon (ARM, M1, M2, ...)?
22
-
23
-
Maybe. Your mileage may vary.
24
-
25
-
In general, PythonCall and JuliaCall are only supported on platforms with
26
-
[Tier 1](https://julialang.org/downloads/#supported_platforms) level of support by Julia.
27
-
Currently, Apple silicon is Tier 2, so is not supported.
28
-
29
-
Due to time constraints, issues affecting only unsupported platforms will not be
30
-
investigated. It is much more likely to be an issue with Julia itself than PythonCall.
31
-
32
21
## Issues when Numpy arrays are expected
33
22
34
23
When a Julia array is passed to Python, it is wrapped as a [`ArrayValue`](#juliacall.ArrayValue).
0 commit comments