Im having trouble getting our python configuration working from within the deadlineslave executable. In dpython everything works fine.
Due to the inability to print during the config initialization, its hard to troubleshoot whats going on :-\
Seems like the python environment now has:
PYTHONPATH=C:\Program Files\Thinkbox\Deadline7\bin\lib;C:\Program Files\Thinkbox\Deadline7\bin\Dlls
Which means any subprocess we start that uses python26 fails :-\
In Deadline 6, the python environment would have had this, which would have pointed to Deadline 6’s Python 2.6 installation:
PYTHONPATH=C:\Program Files\Thinkbox\Deadline6\bin\lib;C:\Program Files\Thinkbox\Deadline6\bin\Dlls
It would be preferred to not have to set this variable, so I wonder if we could use a .pth file in the site-packages folder instead of setting PYTHONPATH…
That might be better if it works, as currently we would have to modify all our code that runs within python to first remove the PYTHONPATH entry from the environment variables…
I think we have a lead on this. Python has a global flag that can be used to tell it to ignore the python environment (PYTHONHOME and PYTHONPATH), and from some initial tests on Windows, it seems to work. However, because we’re p/invoking the python27.dll from .NET, we have to add a function to python to set this flag because we can’t work with the global variable directly. This means that we need to rebuild python, as well as do some testing on Linux and OSX.
Just wanted to give you an update.
Cheers,
Ryan
Thanks Ryan!