-
Notifications
You must be signed in to change notification settings - Fork 188
Closed
Description
I was trying to change the Python executable from the one used by default to one in a Miniconda virtual environment that has already been created.
I followed the steps in README.md, but PyCall.jl seems to "ignore" me. I show here what happens:
julia> using PyCall; using Pkg
julia> ENV["PYTHON"] = "/opt/homebrew/Caskroom/miniconda/base/envs/intel_env/bin/python3"
"/opt/homebrew/Caskroom/miniconda/base/envs/intel_env/bin/python3"
julia> Pkg.build("PyCall")
Building Conda ─→ `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/b19db3927f0db4151cb86d073689f2428e524576/build.log`
Building PyCall → `~/.julia/scratchspaces/44cfe95a-1eb2-52ea-b672-e2afdf69b78f/9816a3826b0ebf49ab4926e2b18842ad8b5c8f04/build.log`
julia>Then after restarting Julia I try to see if the change have been performed and:
julia> using PyCall
julia> PyCall.python
"/Users/antoniomoralesperez/.julia/conda/3/aarch64/bin/python"
julia>So, nothing has changed. It is strange because I have done this successfully in the past. Finally, here is some more info about my installation:
julia> versioninfo()
Julia Version 1.11.3
Commit d63adeda50d (2025-01-21 19:42 UTC)
Build Info:
Official https://julialang.org/ release
Platform Info:
OS: macOS (arm64-apple-darwin24.0.0)
CPU: 8 × Apple M2
WORD_SIZE: 64
LLVM: libLLVM-16.0.6 (ORCJIT, apple-m2)
Threads: 1 default, 0 interactive, 1 GC (on 4 virtual cores)
julia>Metadata
Metadata
Assignees
Labels
No labels