Avoid adding conda on system env variable
Closed this issue · 5 comments
Having to add conda on the systen env is a little bit annoying. It should be possible to do as @lacan does in QuPath and @jytinevez does in trackmate: simply specifying the python executable location should be enough to execute a background task on the proper conda env.
This needs to be tested ideally on all platform, and with or without gpu (grmpflm rogntudju).
This change may be a little annoying for bwd compatibility... Ideally we find a way to fix the wrong path automatically.
Also: it should be possible to get rid of the disctinction between conda and venv with this modification.
Potentially expected pitfalls: if the env needs to override system env variable, it could be that running the python executable skips this part. Hopefully there's a chance that we don't care.
When implementing this for DeepSlice, it seems that I get this kind of error:
https://stackoverflow.com/questions/36778066/importerror-dll-load-failed-when-importing-numpy-installed-in-conda-virtual-env
maybe the option is to add the msvc_runtime in the conda env. Not sure
And I can't even conda install msvc_runtime in the deepslice env