The title says it all. I have a .hip file containing nodes with code that relies on external libraries to run. In my 123.py and 456.py files I handle loading the needed libraries into the environment, however since the scene file will load into memory before the startup scripts run, I get a bunch of nasty errors. The scene will still work fine once the UI opens up, but the errors tend to scare the artists.
The only way I know to work around this is to either permanently add the libraries to the system environment, or launch Houdini from a script that initialized the environment beforehand.
The problem with approach 1 is that IT doesn't want me screwing around with the system environment.
The problem with approach 2 is that I can't figure out how to do this and still allow artists to open files via double-clicking the .hip.
Any ideas? Perhaps just letting the error's happen is the lesser evil?
Custom code in .hip file throw errors before startup scripts have had a chance to add needed libraries to the Python Path.543 4 2
- Quick Links