topic Hi Todd, in Intel® Distribution for Python*

Hardcoded windows paths in scripts in Intel® Distribution for Python 2017 Update 2

gaston-hillar — Fri, 24 Mar 2017 17:44:50 GMT

The activate and deactivate scripts included in Intel® Distribution for Python 2017 Update 2 for Windows include hardcoded Windows paths that don't allow the scripts to work as expected.

If you go to the Scripts folder and check the contents of the activate.bat file, you will find a hardcoded path C:\TCAgent1\tools\Miniconda3\Scripts

The following is the content for the activate.bat file:

@echo off
call "C:\TCAgent1\tools\Miniconda3\Scripts\activate" %*

The following is the content for the deactivate.bat file:

@echo off
call "C:\TCAgent1\tools\Miniconda3\Scripts\deactivate" %*

The activate and deactivate files that are not intended to be executed on Windows also have the same Windows hardcoded path.

The contents for the files with the same names included in the pkgs\conda-4.2.12-py27_intel_0\Scripts folder also have the same issues.

This thread is related to

gaston-hillar — Fri, 24 Mar 2017 17:49:35 GMT

This thread is related to another thread that was started with a different description. I've created this thread as a bug report because I've checked an there is a bug with the Windows version. The following is the related thread: https://software.intel.com/en-us/forums/intel-distribution-for-python/topic/721042

It is a very important issue because the hardcoded path doesn't allow the activate and deactivate scripts to run. I haven't tested it, but it might also affect other OSs in case the same source was used.

Just to clarify, activate.bat

gaston-hillar — Fri, 24 Mar 2017 18:17:26 GMT

Just to clarify, activate.bat works without issues in Intel® Distribution for Python 2017 Update 2 - Python 3.5.2. The problem is only with Python 2.7.12.

Gaston,

Todd_T_Intel — Fri, 24 Mar 2017 18:21:17 GMT

Gaston,

Thank you for bringing this to our attention. We are working on a fix for this.

In the meantime, you can install an updated conda package from the default channel on anaconda.org:

<path_to_install_dir>\Scripts\conda install conda=4.2.12=py27_0
That command will replace the existing "conda" package with the same version from the "defaults" channel, which does not have the problem.

Thank you for your understanding.

Todd

Hi Todd,

gaston-hillar — Fri, 24 Mar 2017 18:24:32 GMT

Hi Todd,

I've run the command you explained and it works OK. Thanks for your workaround. It is extremely helpful.

Follow-up:

Todd_T_Intel — Tue, 04 Apr 2017 20:54:19 GMT

Follow-up:

There is a fixed version of the Windows conda package for python 2.7 available on the Intel channel on anaconda.org under a special label. You can install the fixed package from the command prompt with the following command:

> conda install conda=4.2.12 -c intel/label/conda

Todd

Hi Todd,

gaston-hillar — Wed, 05 Apr 2017 21:43:47 GMT

Hi Todd,

Thanks for the follow up.