Revision history [back]
This occurs on Windows (at least) when Anaconda is installed without setting PATH. It occurs both inside Wing and if Anaconda is run from the command line. The option to set PATH during installation is disabled by default in the installer but the problems can be avoided by enabling it. However, enabling it only works for one installation at a time and might cause conflicts if running multiple installations of Anaconda.
Another work-around is to run Scripts\activate in the Anaconda installation on the command line and then start Wing from the command line within that activation. This causes Wing to inherited the necessary PATH env.
Or you can add to PATH in Wing's Project Properties with something similar to this:
ANACONDA_DIR=c:\Users\whoever\AppData\Local\Continuum\anaconda3
PATH=${PATH};$(ANACONDA_DIR);${ANACONDA_DIR}\DLLS;${ANACONDA_DIR}\Library;${ANACONDA_DIR}\Library\bin;${ANACONDA_DIR}\Scripts;${ANACONDA_DIR}\mingw-w64\bin
The advantage of the latter is that you don't need to quit and restart Wing if switching Anaconda installations.
This occurs on Windows (at least) when Anaconda is installed without setting PATH. It occurs both inside Wing and if Anaconda is run from the command line. The This option to set PATH during installation is disabled by default in the installer but the problems can be avoided by enabling it. However, enabling it only works for one installation at a time and might cause conflicts if running multiple installations of Anaconda.it.
Another work-around is to run Scripts\activate in the Anaconda installation on the command line and then start Wing from the command line within that activation. This causes Wing to inherited the necessary PATH env.
Or you can add to PATH in Wing's Project Properties with something similar to this:
ANACONDA_DIR=c:\Users\whoever\AppData\Local\Continuum\anaconda3
PATH=${PATH};$(ANACONDA_DIR);${ANACONDA_DIR}\DLLS;${ANACONDA_DIR}\Library;${ANACONDA_DIR}\Library\bin;${ANACONDA_DIR}\Scripts;${ANACONDA_DIR}\mingw-w64\bin
The advantage of the latter is that you don't need to quit and restart Wing if switching Anaconda installations.
This occurs on Windows (at least) are least when Anaconda is installed without setting PATH. This option is disabled by default in the installer but the problems can be avoided by enabling it.
Another work-around is to run Scripts\activate in the Anaconda installation on the command line and then start Wing from the command line within that activation. This causes Wing to inherited the necessary PATH env.
Or you can add to PATH in Wing's Project Properties with something similar to this:
ANACONDA_DIR=c:\Users\whoever\AppData\Local\Continuum\anaconda3
PATH=${PATH};$(ANACONDA_DIR);${ANACONDA_DIR}\DLLS;${ANACONDA_DIR}\Library;${ANACONDA_DIR}\Library\bin;${ANACONDA_DIR}\Scripts;${ANACONDA_DIR}\mingw-w64\bin
The advantage of the latter is that you don't need to quit and restart Wing if switching Anaconda installations.