Jörg Budischewski wrote:
Suggested solution:
Whenever the pythonloader tries to load a new python unocomponent, it looks
beside the uno component for a file with the
name pythonpath.zip. If it exists, it puts it into sys.path (if it is not
already in there). Afterwards, it loads
the given component. You can put everything you want to have in
PYTHONPATH into
this zip-file. This is necessary,
as otherwise every file with a .py suffix would be interpreted as a python
component, packages would fail during the
registration process.
The extension manager (and thus unopkg) should only try to register as
UNO components those .py files in an extension that are mentioned with
the appropriate MIME type in the extension's manifest. Other .py files
should merely be unpacked into the extension's target directory. So no
need to hide the .py files in an extra zip, I'd think.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
