comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
Home » Public Forums » archive » New free DLL for calling Python from IDL!
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend  		Return to the default flat view Create a new topic Submit Reply
Re: New free DLL for calling Python from IDL! [message #88454 is a reply to message #87887] Mon, 28 April 2014 12:06 Go to previous messageGo to previous message
Jason Ferrara is currently offline  Jason Ferrara
Messages: 17
Registered: February 2008
Junior Member
Paths shouldn't matter. The standard Python windows installers drop a dll into \Windows\system32. The name of the dll includes the Python version, so that installs of different Python versions can coexist. When Slither loads it loads appropriate dll from \Windows\system32, and then the dll knows how to find the rest of the Python install.

Make sure that if you start Python from the command line you can do "import numpy" without it crashing. If there is something wrong with your numpy install Slither won't load correctly.

On Tuesday, April 15, 2014 7:06:13 PM UTC-4, Helder wrote:
>
>
> Hi,
>
> well, first thanks to all Dick, Yuxi and David.
>
> Unfortunately, it's still not working. Here is the summary of what I have tried.
>
>
>
> I installed python 2.7 and 3.3 (WinPython). I made sure I had the right path for the right test. Meaning if I started python from the command line I would either get version 2.7 or 3.3 depending on how I modified the windows path.
>
>
>
> I made new directories where I put the Slither dll and dlm files (for versions 2.7 and 3.3 in separate dirs!).
>
>
>
> Removed the old Slither dll and dlm files.
>
>
>
> Tried pyimport and without setting the path and it did not work as expected.
>
> I set the path in IDL and windows to python 2.7 and Slither and tried pyimport -> sudden crash. No info, no warning.
>
>
>
> Same happens for python 3.3.
>
>
>
> If I remove the windows path, so that I cannot start python from the command line without going in the specific directory, I still get a total crash. So apparently it isn't even getting to start python or communicate with it.
>
>
>
> Although it's pretty late (1 am), I'm quite sure I didn't screw up the paths in windows and idl. I double checked this in windows from the command line and in idl I made restarted.
>
>
>
> I'll think about this tomorrow, but I don't see how Anaconda could be better/different.
>
>
>
> Thanks again for your help.
>
>
>
> 'night,
>
> Helder

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: superresolution
Next Topic: How to find the confidence interval of a variable data at 95% or 66%?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 20:08:33 PDT 2025

Total time taken to generate the page: 0.37053 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.7.
Copyright ©2001-2013 FUDforum Bulletin Board Software