On Mon, Apr 30, 2012 at 8:25 PM, Piotr Ożarowski wrote:
>
> What hack? Do not change anything in plugins or in the startup script.
> Systems with public programlib already work and on those with private
> dir, external plugins will have to be installed with
> PYTHONPATH=/usr/share/program/ and --
[BRAGA, Bruno, 2012-04-30]
> > > 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 sh
On Mon, Apr 30, 2012 at 7:55 PM, Piotr Ożarowski wrote:
> [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
> > |
> > |--
[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/
> | |
>
Dear Gurus,
I have a question about plugins structure, and I would like to get some
advise from you. It is basically related to how I can reach a private
module (for python applications) while compiling a plugin that uses that
module.
I have an application to which I would like to add some extern
5 matches
Mail list logo
