Great writeup, Jesse. My ultimate goal is keep 3rd party dependencies separate for each maya-python project.
Are you sure virtualenv is what you want for this? The most common approach I’ve come across is by modifying the environment variables upon application startup. In the case of Maya, on Windows, it could be as simple as: set MAYA_SHELF_PATH=%MAYA_SHELF_PATH%;\\myserver\pipeline\Maya\Shelvesset MAYA_PLUG_IN_PATH=%MAYA_PLUG_IN_PATH%;\\myserver\pipeline\Maya2015set PYTHONPATH=%PYTHONPATH%;\\myserver\pipeline\tools;\\myserver\pipeline\Systemset MAYA_SCRIPT_PATH=%MAYA_SCRIPT_PATH%;\\myserver\pipeline\Maya\Scripts "C:/Program Files/Autodesk/Maya2015/bin/maya.exe" %* You’d then run this, instead of maya.exe directly, and thus inject it with these environment variables. You can then customise which projects are exposed to which libraries and plug-ins by simply having a script like this for each project. project1_maya.bat project2_maya.bat project2_softimage.bat ... -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmODugLm8x8iXhghQmDXXkBU%3DbZa-VaS2qpagSLR%3DU%2BZCAg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
