Closed manuel-koch closed 3 days ago
Maybe my expectation of pyenv virtualenv
with miniconda
is plain wrong and it is expected to not work ?
My naive assumption is that I can create a virtualenv of any installed python interpreter.
Looks like the virtualenv is using some other previously installed miniconda ( miniconda3-latest
in my case ).
# CWD in ~/tmp/my_conda
$ conda info
/Users/manuelkoch/.pyenv/versions/miniconda3-latest/lib/python3.11/site-packages/conda/base/context.py:198: FutureWarning: Adding 'defaults' to channel list implicitly is deprecated and will be removed in 25.3.
To remove this warning, please choose a default channel explicitly with conda's regular configuration system, e.g. by adding 'defaults' to the list of channels:
conda config --add channels defaults
For more information see https://docs.conda.io/projects/conda/en/stable/user-guide/configuration/use-condarc.html
deprecated.topic(
active environment : /Users/manuelkoch/.pyenv/versions/miniconda3-3.12-24.9.2-0/envs/my_conda-3.12
active env location : /Users/manuelkoch/.pyenv/versions/miniconda3-3.12-24.9.2-0/envs/my_conda-3.12
shell level : 0
user config file : /Users/manuelkoch/.condarc
populated config files :
conda version : 24.9.2
conda-build version : not installed
python version : 3.11.5.final.0
solver : libmamba (default)
virtual packages : __archspec=1=m1
__conda=24.9.2=0
__osx=14.7.1=0
__unix=0=0
base environment : /Users/manuelkoch/.pyenv/versions/miniconda3-latest (writable)
conda av data dir : /Users/manuelkoch/.pyenv/versions/miniconda3-latest/etc/conda
conda av metadata url : None
channel URLs : https://repo.anaconda.com/pkgs/main/osx-arm64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/osx-arm64
https://repo.anaconda.com/pkgs/r/noarch
package cache : /Users/manuelkoch/.pyenv/versions/miniconda3-latest/pkgs
/Users/manuelkoch/.conda/pkgs
envs directories : /Users/manuelkoch/.pyenv/versions/miniconda3-latest/envs
/Users/manuelkoch/.conda/envs
platform : osx-arm64
user-agent : conda/24.9.2 requests/2.31.0 CPython/3.11.5 Darwin/23.6.0 OSX/14.7.1 solver/libmamba conda-libmamba-solver/24.9.0 libmambapy/1.5.8
UID:GID : 501:20
netrc file : None
offline mode : False
It's more like conda uses some metadata cache in a shared location.
The immediate reason is the conda command pyenv-virtualenv
runs: conda create <...> --yes <..> python
Which makes it use the latest Python in its metadata.
We should probably read the version of the Python package in the base environment and instruct it to install that.
Description
Installing python interpreter using
Detailed output: