|
The sys.path list can be appended to easily if done before importing a module, and the launcher wrapper has a self.appdir that will allow the path to the python3lib to be built on the fly easily (See EmbeddedPython.cpp embeddedRoot() routine - or something like that) on Windows and Mac. I am less sure where exactly on Linux the python3lib ends up depending on build settings.
So it would be easy to do with current code in a plugin on Windows and Mac, but I am not sure how easy it would be on Linux.
Diapdealer - is there any way to figure out where the python3lib is located in the current launcher or wrapper plugin code given what we pass in the sigil.cfg file?
|