James Fort wrote:
Thanks a lot for your replies. I discovered the source of the problem. When I first set up this new Python installation I noticed that it wasn't able to execute at all from a command prompt, so I created a batch file to launch the executable and put the batch file into a totally unrelated directory that was already being referenced in my PATH environment variable.
that would do it.
My company's software is actually called Abaqus
the FEA software? that looks pretty cool, and the python scripting would be very cool!
It is installed inside the Abaqus installation directory, not the default location
as it should be - good.
Incidentally, I found out today that setting the PYTHONPATH variable in Windows allows my two different installations of Python to access the same modules. I was very happy to discover that. :)
Handy for you but that could be a pain if you are running incompatible versions. Personally, I avoid PYHONPATH anyway.
-Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [email protected]
