Running python.exe (v3.10) from a conda environment results in zlib.dll missing error #11072
Description
Checklist
- I added a descriptive title
- I searched for other issues and couldn't find a solution or duplication
- I already searched in Google and didn't find any good information or help
- I looked at the docs and didn't see anything to help
What happened?
Create two environments:
conda create -p conda_py310 python=3.10
conda create -p conda_py39 python=3.9
with the python 3.9 environment you can execute python binary directly if needed. With the 3.10 environment you cannot.
Conda info
C:\GIT>conda info
active environment : None
user config file : C:\Users\Karthik Nadig\.condarc
populated config files :
conda version : 4.10.3
conda-build version : not installed
python version : 3.8.3.final.0
virtual packages : __cuda=11.4=0
__win=0=0
__archspec=1=x86_64
base environment : C:\ProgramData\Miniconda3 (writable)
conda av data dir : C:\ProgramData\Miniconda3\etc\conda
conda av metadata url : None
channel URLs : https://repo.anaconda.com/pkgs/main/win-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/win-64
https://repo.anaconda.com/pkgs/r/noarch
https://repo.anaconda.com/pkgs/msys2/win-64
https://repo.anaconda.com/pkgs/msys2/noarch
package cache : C:\ProgramData\Miniconda3\pkgs
C:\Users\Karthik Nadig\.conda\pkgs
C:\Users\Karthik Nadig\AppData\Local\conda\conda\pkgs
envs directories : C:\ProgramData\Miniconda3\envs
C:\Users\Karthik Nadig\.conda\envs
C:\Users\Karthik Nadig\AppData\Local\conda\conda\envs
platform : win-64
user-agent : conda/4.10.3 requests/2.26.0 CPython/3.8.3 Windows/10 Windows/10.0.19041
administrator : True
netrc file : None
offline mode : FalseConda config
C:\GIT>conda config --show-sources
C:\GIT>Conda list
C:\GIT>conda list --show-channel-urls
# packages in environment at C:\ProgramData\Miniconda3:
#
# Name Version Build Channel
brotlipy 0.7.0 py38h2bbff1b_1003 defaults
ca-certificates 2021.10.26 haa95532_2 defaults
certifi 2021.10.8 py38haa95532_0 defaults
cffi 1.15.0 py38h2bbff1b_0 defaults
charset-normalizer 2.0.4 pyhd3eb1b0_0 defaults
conda 4.10.3 py38haa95532_0 defaults
conda-package-handling 1.7.3 py38h8cc25b3_1 defaults
console_shortcut 0.1.1 4 defaults
cryptography 35.0.0 py38h71e12ea_0 defaults
idna 3.3 pyhd3eb1b0_0 defaults
menuinst 1.4.16 py38he774522_0 defaults
openssl 1.1.1l h2bbff1b_0 defaults
pip 21.2.2 py38haa95532_0 defaults
powershell_shortcut 0.0.1 3 defaults
pycosat 0.6.3 py38h2bbff1b_0 defaults
pycparser 2.21 pyhd3eb1b0_0 defaults
pyopenssl 21.0.0 pyhd3eb1b0_1 defaults
pysocks 1.7.1 py38haa95532_0 defaults
python 3.8.3 he1778fa_0 defaults
pywin32 228 py38hbaba5e8_1 defaults
requests 2.26.0 pyhd3eb1b0_0 defaults
ruamel_yaml 0.15.100 py38h2bbff1b_0 defaults
setuptools 58.0.4 py38haa95532_0 defaults
six 1.16.0 pyhd3eb1b0_0 defaults
sqlite 3.36.0 h2bbff1b_0 defaults
tqdm 4.62.3 pyhd3eb1b0_1 defaults
urllib3 1.26.7 pyhd3eb1b0_0 defaults
vc 14.2 h21ff451_1 defaults
vs2015_runtime 14.27.29016 h5e58377_2 defaults
wheel 0.37.0 pyhd3eb1b0_1 defaults
win_inet_pton 1.1.0 py38haa95532_0 defaults
wincertstore 0.2 py38haa95532_2 defaults
yaml 0.2.5 he774522_0 defaults
C:\GIT>Additional Context
In the python extension for VS Code we try to get information about python binary by running a script using just the binary directly. This allows us to detect information about the environment, before we can figure out if it is conda based or venv based etc. This seems like a bug with the binary that is being shipped, since we can't execute scripts that don't depend on installed libraries.