Currently, the Python implementation requires that a script file using the eMach objects be located at a certain relative path (i.e. examples folder needs to be located in the python folder, it cannot be in python\eMach). This isn't going to be a workable solution for people who use eMach via a git submodule.
One solution would be to permanently alter the python path environmental variable, but this seems a bit heavy handed and would require a user to do this every time they move their project to a different location on their hard drive.
Is there a more moderate compromise here? In MATLAB we can add folders to that path that only persist their until we restart MATLAB. Can we do something similar in Python?
Currently, the Python implementation requires that a script file using the eMach objects be located at a certain relative path (i.e.
examplesfolder needs to be located in thepythonfolder, it cannot be inpython\eMach). This isn't going to be a workable solution for people who useeMachvia agit submodule.One solution would be to permanently alter the python path environmental variable, but this seems a bit heavy handed and would require a user to do this every time they move their project to a different location on their hard drive.
Is there a more moderate compromise here? In MATLAB we can add folders to that path that only persist their until we restart MATLAB. Can we do something similar in Python?