Christopher Rowley

PythonCall's special support for pandas is basically: - a function to convert a Julia table to a pandas dataframe - a wrapper type for a pandas dataframe which satisfies the...

This is a very mysterious error. It's to do with signal handlers - and getting Python and Julia to co-operate on signal handling is hard. I don't really know where...

Hmm. When we wrap Julia values into Python objects, the Julia object is stored in a global vector and referred to by index from the Python object. It seems that...

Honestly I don't know - just the nature of the error suggests the state is corrupted, which suggests some race condition. You could try that branch and see. The state...

It's because if you have created and instantiated a Julia project (JuliaCall requires the project to be instantiated) then you already have a Julia executable to do that - in...

> That's annoying. That's just how Julia works - if someone gives you a Project.toml and a Manifest.toml, you have to instantiate it first. JuliaCall intentionally doesn't touch Pkg itself,...

I don't think I'm going to add another backend to PythonCall because this will just fragment things. However CondaPkg by default does now use Pixi which in turn uses uv...

The problem is that even if your project only has python dependencies, some package that you use might have conda dependencies. CondaPkg collects these all together and installs them all....

All good points! Just on this specific one: > the fact that it is unified internally is moreso interesting to developers (us) rather than to someone wanting to call a...

As @MilesCranmer already explained elsewhere there is no inconsistency here. Since Python has no inbuilt notion of multidimensional arrays, numpy allows you to construct an array from a list of...