Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove M1/M2 part from FAQ #444

Merged
merged 1 commit into from
Jan 27, 2024
Merged

Remove M1/M2 part from FAQ #444

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions docs/src/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,17 +18,6 @@ Some rules if you are writing multithreaded code:

Related issues: [#201](https://github.com/JuliaPy/PythonCall.jl/issues/201), [#202](https://github.com/JuliaPy/PythonCall.jl/issues/202)

## Does it work on Apple silicon (ARM, M1, M2, ...)?

Maybe. Your mileage may vary.

In general, PythonCall and JuliaCall are only supported on platforms with
[Tier 1](https://julialang.org/downloads/#supported_platforms) level of support by Julia.
Currently, Apple silicon is Tier 2, so is not supported.

Due to time constraints, issues affecting only unsupported platforms will not be
investigated. It is much more likely to be an issue with Julia itself than PythonCall.

## Issues when Numpy arrays are expected

When a Julia array is passed to Python, it is wrapped as a [`ArrayValue`](#juliacall.ArrayValue).
Expand Down
Loading