| 28 Aug 2015 10:27 AM |
|
|
Hello,
I added my python installation "C:\python34" to PATH system environment variable, but it shows like this:
IDL> PRINT, Python.Run('[x*x for x in range(1,11)]')
% PYTHON::LOAD: Unable to find a valid Python installation.
% Execution halted at: $MAIN$
IDL helping doc says "You should ensure that your Python executable is on the Windows system PATH environment variable. IDL will use the first Python executable that it finds on the system path."
Did I do the right thing to config the IDL to python bridge ?
thanks.
|
|
|
|
Deleted User
New Member
Posts:  
| 28 Aug 2015 08:48 PM |
|
|
I installed the Anaconda then, now IDL-python bridge works well for each other, thanks.
|
|
|
|
Deleted User
New Member
Posts:
| 01 Sep 2015 02:58 AM |
|
|
Hello,
I got the same answer having "C:\python34" in the path of Windows!!! No problem with Anaconda on Yosemite....
Didier
|
|
|
|
Zachary Norman
Basic Member
Posts:173 
| 08 Sep 2015 09:00 AM |
|
|
Hi All,
Which version of Python are you using? Just the standard Python 3.4 or Python 2.7 distribution? The first thing to check is that you indeed have the python executable on the search path. Open up a command prompt and see if you can successfully call Python. You must also be able to call IDL from the command prompt as well, which means you should have some additional environment variables set. These should be (from a batch file I use):
set PATH=C:\Anaconda;C:\Program Files\Exelis\IDL85\bin\bin.x86_64;%PATH%
set PYTHONPATH=C:\Program Files\Exelis\IDL85\bin\bin.x86_64;C:\Program Files\Exelis\IDL85\lib\bridges
Also, you must start IDL from a command line, you cannot click on the icon for the Workbench and expect IDL to pull in your environment variables. You may also need to specify the PYTHONHOME variable in addition to the ones above. It depends on the Python distribution and how you installed it if you need that or not. Another good thing to mention is that you will nee the numpy module for Python in order to use the IDL-Python bridge.
|
|
|
|