Christopher Rowley

No the current behaviour is intended, and is indeed for ABI compatibility. The bounds are chosen assuming that the Julia OpenSSL package is loaded before the Python one. Suppose that...

You can now set `JULIA_CONDAPKG_OPENSSL_VERSION=ignore` if you'd like to turn off this behaviour. See the README for more info.

Hiya, sorry to not pick this up for a while. I actually read through this a while ago and had some reservations but forgot to reply! It certainly seems reasonable...

Yep the example was using your branch, but I made some modifications playing around with it to see what worked. I think what actually might be a nice simple generic...

Indeed the semantics of how Julia and Python threads interact have not been totally worked out yet. In particular, Julia has a task scheduler which doesn't really like running on...

@nilsdeppe yep something along those lines seems reasonable, I've opened a separate issue about it.

It's true that Python code is not currently interruptible when called from PythonCall. That requires some signal handling magic that I think isn't currently possible in Python and Julia. In...

It appears that neither setting is ideal, but the current default (`no`) is less intrusive to non-Julia Python code. Here is a Python session with the default (`no`), where I...

Agreed that a setting to prefer existing installations would be good. In the meantime you can set the environment variable `PYTHON_JULIAPKG_EXE` to a specific Julia if you want to avoid...

Nice idea but.... This would be really non-trivial to implement - for example the name of a package in PyPI can be different from its name in Conda, so getting...