PythonCall.jl
PythonCall.jl copied to clipboard
JuliaPy
Python and Julia in harmony.
- unsafe functions (e.g. pynew, pycopy!, unsafe_pynext, PyNULL) - can mostly be avoided already; could have a safe pynext which returns `nothing` if iteration has finished - CONFIG - C.CTX...
- Similar to CondaPkg, we can support both env vars and preferences. - If CondaPkg is not needed, don't import it.
As I believe that it is not necessary when `JULIA_CONDAPKG_BACKEND=Null`. Relevant for Julia >= 1.9.
- switch to using explicit branching logic, instead of lookups of functions? - prefer copying over wrapping? e.g. `list` to `Vector` not `PyVector`? - arguments for finer control? e.g. `copy=true`...
**Is your feature request related to a problem? Please describe.** Python stack traces place the most recent call last, Julia's place the most recent call first. When I the call...
I want to get my hands on a `Tuple{Float32, Float32}` in Python and there doesn't seem to be a good way of doing it ```pycon >>> jl("typeof")(jl("Tuple{Float32, Float32}")((0.0, 1.0))) Julia:...
1. Identify which bits of PythonCall only depend on the Stable ABI and which bits depend on internals. 2. Work towards only using the Stable ABI.
**Affects:** JuliaCall **Describe the bug** An example of this that I ran into is that everything is reported as itterable, even when it cannot be iterated. This looks pretty bad...