OS

• Windows

Limitations

• Currently only looks for installations fromPythonCore andContinuumAnalytics keys.Should we look iterate through all the keys underHKLM/Software &HKCU/Software ?@karthiknadig /cc

Pseduo code for algorithm

forcompanyof[PythonCore,ContinuumAnalytics]:foreachkeyin[HKLM,HKCU]:foreachinstalled_versionin`<key>/Software/Python/<company>`// installed_version are values like 3.12, 3.10, 3.9, etcinstall_key=`<key>/Software/Python/<company>/<installed_version>InstallPath`env_path=`install_key/(Default)`exe=`install_key/(ExecutablePath)`ifcompany==PythonCoreand`exe`existsondisc:version=`install_key/(Version)`// SysVersion contains only first 2 parts of versiondisplay_name=`install_key/(DisplayName)`👍trackthisenvironmentelseifcompany==ContinuumAnalyticsand`exe`existsondisc:Wetreatthisasacondaenv👍Nowuse`conda`algorithmtogetallcondaenvironmentsunderthedirectory`env_path`.

OS

• Windows

Limitations

• No way to get the full version (we can only get the first two part of the version)

Pseduo code for algorithm

foreachdirectoryunder`<home>/AppData/Local/Microsoft/WindowsApps`:ifdirectorydoesnotstartwith`PythonSoftwareFoundation.Python.`:continueif `python.exe` does not exists in the directory:        continue    app_model_key = `HKCU/Software/Classes/LocalSettings/Software/Microsoft/Windows/CurrentVersion/AppModel`;    package_name = `<app_model_key>/SystemAppData/<directoryname>/Schemas/(PackageFullName)`    key = `<app_model_key>/Repository/Packages/<package_name>`    env_path = `<key>/(PackageRootFolder)`    display_name = `<key>/(DisplayName)`    exe = `python.exe`// No way to get the full version information.👍trackthisenvironment

OS

• MacOS
• Linux

Notes

• Install folders & symlinks documented herehttps://formulae.brew.sh/formula/python@3.9
• Homebrew install locations documented herehttps://docs.brew.sh/Installation

Pseduo code for algorithm

homebrew_dir=findthisfolder(either`HOMEBREW_PREFIX`ordefaulttodirectorydefinedherehttps://docs.brew.sh/Installation)foreachfileunder`<homebrew_dir>/bin`:ifwehaveapythonexecutableanditsasymlink,thenproceedifnot,thenskipthisfileresolvethesymlinkandverifythefile isinoneoftheknownhomebrewdirectories.ifnot,thenskipthisfileExtracttheversionfromthefilepath.Computetheenv_pathbyextractingtheversioninformation.Theenv_path isknowndirectoriesonMacOS(Intel&Silicon)andLinux.

OS

• MacOS
• Linux
• Windows

Notes

• Structure of conda envionment
  • A conda install folder will have a default environment with Python
  • theenvs sub directory in a conda installation contains all conda environments belonging to that conda installation
• Conda environments
  • This is computed from a list of hardcoded locations (for windows, linux, macos)
  • This includes locations in.condarc file
  • This includes locations inenvironments.txt file
  • This includes all sub directories under theenv directory in the all known conda installation folders
• .condarc
  • The.condarc file can be configured to store conda environments in other locations instead of<conda install folder>/envs
  • There can be multiple conda installations on a machine, each with its own set of environments
  • There can be multiple directories defined in.condarc file to store conda environments
  • Theenvironments.txt contains all known conda environments on the current machine (including base env, which is the same as install location of conda)
  • The directories returned byconda info --json are the directories where conda environments are stored
• Version of conda can be found in<conda install folder>/conda-meta/conda-<version>.json file
• User can install multiple versions of conda,
  • In usual (default) locations & also in custom locations
  • Also can be installed via pyenv, in which case the conda installations are located under~/.pyenv/versions/<conda install version>
• conda-meta\<package name>-<version>.json files
  • This contains information about all conda packages installed into a conda environment.
  • The root (base) conda environment too has such a directory.
  • Givenconda is a package in its own right, the version of conda can also be found in theconda-meta directory.
    (after all, you can update conda usingconda update conda).
  • Similarly if Python is installed in a conda environment, the version of Python can be found in theconda-meta directory.
• conda-meta\history file
  • This contains a history of all installations of this conda environment.
  • One key information is the command used to create the conda environment itself.
  • The entry looks like so# cmd: /Users/donjayamanne/.pyenv/versions/miniconda3-latest/bin/conda create -n myenv python=3.10
  • Thus using thehistory file we can find the conda installation folder.This is useful in cases where conda environments are created using-p option.

What if conda is installed in some custom locations that we have no idea about?In such cases the assumption is that theenvironments.txt file will contain an entry to the base env.Using that information we can get the conda directory and get the conda exe and version info.

Even ifenvironments.txt file is empty, we will look for environments in known locations and from there we can find the conda install folder (recallhistory file).

What if we have a custom conda env created in current workspace folder, and we do not know where Conda is installed?In such cases we can just inspect theconda-meta/history file in the conda env folder and get the conda installation folder.

How do we generate command to run Python in an environment?If the Conda env is in theenvs folder, then use<conda exe> -n <env name> python.If the Conda env is the root (base) folder, then use<conda exe> -n base python.For all other cases use<conda exe> -p <fully qualified path to folder> python.

Pseduo code for algorithm

// Step 1// Get a list of all known directories where conda environments can be found// 1. environments.txt file// 2. .condarc file// 3. Other known locations// Step 2// We hardcode some of the commonly known install directories of conda, miniconda, miniforge, etc for all platforms.foreachknown_install_folderin[<home>/anaconda3,<home>/miniconda3,etc]:conda_exe=`<known_install_folder>/bin/conda`(windowsisslightlydifferent)conda_version=`<known_install_folder>/conda_meta/conda-<version>.json`python_exe=`<known_install_folder>/bin/python`(windowsisslightlydifferent)python_version=`<known_install_folder>/conda_meta/conda-<version>.json`// Step 2.1// We now have conda exe, version, default python information// Conda run command is computed as `[<fully qualified path to conda_exe>, run, -n, <name> python]`foreachenvin`<known_install_folder>/envs`:// env is a conda environment// Find python exe and version in the conda-meta directory// If python is not found, then this is a conda env without Python.// These are named environments that are activated (run) using the `-n` option.// Previously we captured a list of all known conda envs// Go through those one by one and inspect the conda-meta/history file// And check whether that env was created by this current conda installation// If so, then associate that env with this conda installation// Next remove that env folder from the list captured in step 1.// Step 3// Finally go through all of the remaining conda envs that were captured in step 1// & did not get removed by step 2.1.// Go into the env folder one by one// Inspect the conda-meta/history file and try to find the installation location of the conda by parsing the `cmd:` line.// If we find a conda installation, then process that folder as we did inside step 2.1

OS

• MacOS
• Linux
• Windows

Notes

• Structure of pyenv directory
  • Theversions folder contains all installed versions/copies of Python
• Windows has a separate implementation of pyenv
  • Windows version does not support installation of various flavours of Python, not even conda.
• For Python we only focus on the standard python installations shipped by pyenv.I.e. jython, pypy, etc are not considered.We only look for folders inversions directory that contains just version info.
• The version ofpyenv can be extracted from the file path ofpyenv installation.If installed using homebrew, then this is installed in/opt/hombrew/bin/pyenv,/usr/local/bin/pyenv& that resolves to the real path/opt/homebrew/Cellar/pyenv/2.4.0/libexec/pyenv,/usr/local/Cellar/pyenv/2.4.1/libexec/pyenv

Conda:

• Theversions directory is the only place where Python installations are stored.
• Conda can be installed into theversions directory via pyenv.
• Identifying a conda install is easy, just look for conda exe and a few other files.Once we find such folders, we pass that onto the conda algorithm to get all conda environments.These are treated as conda environments and notpyenv.

Virtual Envs:

• Using the pyenv virtual envs plugin, one can create virtual environments.
• These are also located in the sameversions directory.
• However these have apyvenv.cfg file in the root of the environment.
• When creating virtual envs using this plugin, pyenv creates anenvs directory in the root of the python envionment that was used to create this env.
  I.e. the virtual env is symlinked in~/.pyenv/versions as well as~/.pyenv/<python version>/envs.We never list these environments (under theenvs directory), no need, its just a duplicate.

Commands used to run Python:

• For conda envionments, the commands used to run/activate the envs are generated by the conda algorithm.
• For all others we just use<fully qualified python exe> as the command.

Pseduo code for algorithm

foreachdirinpyenvdirectory:ifdir isacondainstallation folder:// Pass this onto the conda algorithmcontinueversion=extractversionfromfoldernameenv_path=thedirectoryitselfif<dir>/pyvenv.cfgexists:// This is a virtual env in pyenvelse// This is a regulary pyenv installation

OS

• MacOS
• Linux
• Windows

Notes

• They have a.project file in the root of the environmentThis file contains the path to the project directory thats associated with this environment.
• They have a.pyvenv.cfg file in the root of the environmentThis file contains the version of Python used in this environment.
• Very similar tovirtualenvwrapper environments, but the difference is that the project will have aPipfile and/orPipfile.lock files.Pseduo code for algorithm

foreachdiringloballyknowndirectories:if`.project`fileexistsinthedirectory:proceedifthepathinthe`.project`filecontainsa`Pipfile`file:// This is a pipenv environmentversion=extractedfrom`.pyvenv.cfg`file

OS

• MacOS
• Linux
• Windows

Notes

• They are regular Python environments created a specific location
• The location is defined in theWORKON_HOME environment variable.
• Else defaults to~/.virtualenvs
• They too have a have a.project file in the root of the environmentThis file contains the path to the project directory thats associated with this environment.
• They have a.pyvenv.cfg file in the root of the environmentThis file contains the version of Python used in this environment.
• Very similar topipenv environments, but the difference is that the project directory will not havePipfile orPipfile.lock files.Pseduo code for algorithm

foreachdirin$WORKON_HOME:ifthis isnotapipenv environment:proceedif`.project`fileexistsinthedirectory:// This is a virtualenvwrapperversion=extractedfrom`.pyvenv.cfg`file

OS

• MacOS
• Linux
• Windows

Notes

• They have a.pyvenv.cfg file in the root of the environmentThis file contains the version of Python used in this environment.

Pseduo code for algorithm

foreachdirin$WORKON_HOME:version=extractedfrom`.pyvenv.cfg`file

OS

• MacOS
• Linux
• Windows

Notes

• They do not have.pyvenv.cfg file
• They have activation scripts in thebin/scripts directory