Christopher Rowley

@schlichtanders That order should definitely work. Can you give the sequence of steps to reproduce your error? And also give the full error you see.

Ok I see, so the issue is that you (implicitly) resolve the Conda environment in order to build RCall and then load some other packages, which also have Conda dependencies,...

Ok after a discussion on Slack the best approach seems to be to check if the mtime/hash of Manifest.toml changed since the last resolve.

Well firstly, packages shouldn't generally be setting global config such as that env var, though I understand why you're doing it. Over in #219 I suggested adding a warning to...

Your alternatives are to use the `pywith` function or to call `__enter__` and `__exit__` yourself.

Yeah we should at least check for this and issue a better error message (like we do in PythonCall).

The particular error message you're seeing is a bug. As it says, it tried to throw a different (better) error, but that failed for some reason so it threw this...

This is indeed mysterious. ``` >>> from juliacall import Main as jl >>> jl.x = [1,2,3] >>> jl.x Traceback (most recent call last): File "", line 1, in File "C:\Users\chris\.julia\packages\PythonCall\qTEA1\src\jlwrap\any.jl",...

I'm pretty sure this issue is already fixed by this commit https://github.com/JuliaPy/PythonCall.jl/commit/45a75c1ecbf6ae8f5ffd63693083598b8b688358 and is just waiting for the next release - which I've been delaying until I get more test...

Ignoring `JULIA_PROJECT` is intended. You can set `PYTHON_JULIAPKG_PROJECT` and `PYTHON_JULIAPKG_OFFLINE=yes` to get the behaviour you want, I think?