@@ -11,7 +11,7 @@ Some rules if you are writing multithreaded code:
1111 (This is because Julia finalizers can be called from any thread.)
1212- You may still encounter problems.
1313
14- Related issues: [ #201 ] ( https://github.com/cjdoris/PythonCall.jl/issues/201 ) , [ #202 ] ( https://github.com/cjdoris/PythonCall.jl/issues/202 ) )
14+ Related issues: [ #201 ] ( https://github.com/cjdoris/PythonCall.jl/issues/201 ) , [ #202 ] ( https://github.com/cjdoris/PythonCall.jl/issues/202 )
1515
1616## Does it work on Apple silicon (ARM, M1, M2, ...)?
1717
@@ -36,7 +36,7 @@ Python(65251,0x104cf8580) malloc: *** set a breakpoint in malloc_error_break to
3636
3737A solution is to ensure that ` juliacall ` is imported before ` torch ` .
3838
39- Related issues: ( [ #215 ] ( https://github.com/cjdoris/PythonCall.jl/issues/215 ) )
39+ Related issues: [ #215 ] ( https://github.com/cjdoris/PythonCall.jl/issues/215 )
4040
4141## ` ccall requries the compiler ` error when importing some Python libraries
4242On some systems, you may see an error like the following when import e.g. ` matplotlib ` before ` juliacall ` :
@@ -62,4 +62,4 @@ The solution is to either:
6262 * import ` juliacall ` before the other Python library, so that Julia's ` libstdc++ ` is loaded
6363 * use a Python from a conda environment, which will have a newer ` libstdc++ ` that is compatible with Julia's
6464
65- Related issues: ( [ #255 ] ( https://github.com/cjdoris/PythonCall.jl/issues/255 ) )
65+ Related issues: [ #255 ] ( https://github.com/cjdoris/PythonCall.jl/issues/255 )
0 commit comments