Anaconda 5.3 Python 3.7 not compatible with Visual Studio 2017 or VS Code, numpy DLL not found error #10257
Comments
This is incorrect. Successful use of |
|
That a previous version of numpy (really python) didn't require activation it does not hold that future versions will not. |
|
@mingwandroid Well, then you should open another issue, because at least two different IDE projects didn't know that. |
|
Be my guest with pycharm. VSCode does support conda activation correctly in the latest code on GitHub. If there's issues in VSCode after that's released I'll try to see if I can do anything. |
|
@mingwandroid I just tried the latest VSCode installing from the |
|
I didn't say that any released version activates correctly, I said the latest code on github appears to do so. |
|
Source code is not the same thing as a released binary with a version. Projects will have various branches and release processes that introduce delays between code being committed and releases becoming available. I don't know how the VSCode team do this. Of course there's every chance the code is in recent insiders builds, there may still be some bugs in there, but I know from looking at the source it does try to activate properly. One thing that I did spot in the code that may cause an issue is the more global pythonPath value. I think it may get added to the end of PATH still, and when using conda, we don't want VSCode doing that. It should let conda manipulate PATH, and in general PATH modifications should happen to the front of PATH. |
|
Just trying to get one of my IDEs to support Anaconda 5.3. That installer is rebuilt with every new commit., so whatever code there is, it's not doing the trick. Opened an issue in VS Code. |
|
OK thanks for the info. I'll try to keep my eye on this. I want VSCode to work well here too. |
|
I don't know what happened, but I don't get the error anymore in VS Code. I still get it in VS 2017. |
|
I don't know, I don't use VS 2017 for Python, I use VS Code and occasionally PyCharm. |
Uh oh!
There was an error while loading. Please reload this page.
Actual Behavior
When Visual Studio 2017 (VS2017) or Visual Studio Code (VSC) (at least on windows) uses Anaconda 5.3 with Python 3.7,
import numpyfails to find a requireddll:When using VS2017 or VSC:
When using
Anaconda Prompt-activated environment:This does not occur when a Python 3.6 "sub-environment" is used instead within that Anaconda 5.3 environment. It also does not occur with Anaconda 5.2. In other words, activating an anaconda 5.3 environment fixes (hides) the problem, but the problem didn't exist in anaconda 5.2 or previous.
Expected Behavior
Successful importing of numpy should not require activating the conda environment.
Steps to Reproduce
Execute
import numpyfrom VS Code or VS 2017 (interactive or in a script) with Anaconda 5.3 Python 3.7Anaconda or Miniconda version:
5.3.0
Operating System:
Windows 10 Pro, Oct 2018 update
conda infoconda list --show-channel-urlsThe text was updated successfully, but these errors were encountered: