New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running python.exe (v3.10) from a conda environment results in zlib.dll missing error #11072
Comments
Found out about this via microsoft/vscode-python#17941 . |
Additional info, if you create an environment using conda-forge it seems to work as expected:
The issue seems to be specific to environments created via default channel. |
@kenodegard didn't 4.11.0 already come out? https://github.com/conda/conda/releases/tag/4.11.0 |
@brettcannon yes it's been tagged but a patch was necessary for conda-build (conda/conda-build#4333) the new conda-build release was tagged earlier today (https://github.com/conda/conda-build/releases/tag/3.21.7) so we should see 4.11.0/4.11.1 in the defaults channel in the next day or so |
@jezdez, @chenghlee, I think you forgot to port conda-forge/zlib-feedstock#51, conda-forge/zlib-feedstock#52 and conda-forge/zlib-feedstock#53 to defaults channel. |
@isuruf Thanks for the pointer, I'll forward that to the packaging team. |
As @chenghlee mentioned in a chat, we'll fix this by fixing the zlib package in a future update. |
@karthiknadig @brettcannon Can you please try |
I honestly don't have the environment lying around anymore, but maybe @karthiknadig does. |
It works after installing zlib via |
Closing; updating to |
Checklist
What happened?
Create two environments:
with the python 3.9 environment you can execute python binary directly if needed. With the 3.10 environment you cannot.
Conda info
Conda config
Conda list
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.
The text was updated successfully, but these errors were encountered: