Re: Doubt about developing plugins for python applications

[Piotr Ożarowski <piotr@debian.org>]

[BRAGA, Bruno, 2012-04-25]
> When compiling/building the source with setup.py, I encountered the problem
> that separating the plugin as an independent solution:
> 
> program/
>     |
>     |---- setup.py
>     |
>     |---- plugins/
>     |         |
>     |         |--pluginA/
>     |         |
> 
> the setup.py fails (obviously) because it does not find the
> packages/modules from programlib, which are only available to the main
> application source.

does setup.py really need to import programlib? If yes, then invoke it
with PYTHONPATH=/usr/share/program/

[...]
> b) add current installation to python path (eg. /usr/share/program) so the
> plugin can import the programlib packages/modules.

plugins import programlib at runtime only, riht? Startup script is
adding . to the sys.path automaticall so plugins should see programlib,
no?
-- 
Piotr Ożarowski                         Debian GNU/Linux Developer
www.ozarowski.pl          www.griffith.cc           www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645