[tryton-debian] custom modules

[Vincent Bastos]

On Wed, Oct 28, 2015 at 11:27 AM, Mathias Behrle <mathiasb at m9s.biz> wrote:

> * Vincent Bastos: " Re: [tryton-debian] custom modules" (Wed, 28 Oct 2015
>   08:23:30 +1000):
>
> > On Wed, Oct 28, 2015 at 7:48 AM, Vincent Bastos <vincent at lavalab.com.au>
> > wrote:
> >
> > >
> > >
> > > On Wed, Oct 28, 2015 at 7:29 AM, Mathias Behrle <mathiasb at m9s.biz>
> wrote:
> > >
> > >> * Vincent Bastos: " Re: [tryton-debian] custom modules" (Wed, 28 Oct
> 2015
> > >>   06:36:48 +1000):
> > >>
> > >> > On Mon, Oct 26, 2015 at 6:53 PM, Mathias Behrle <mathiasb at m9s.biz>
> > >> wrote:
> > >> >
> > >> > > * Vincent Bastos: " [tryton-debian] custom modules" (Sun, 25 Oct
> 2015
> > >> > > 17:47:22
> > >> > >   +1000):
> > >> > >
> > >> > > > I was wondering what method is used to install custom modules.
> > >> > >
> > >> > > The ITP and packaging of the custom module will start as soon as
> it
> > >> will be
> > >> > > released.
> > >> > >
> > >> >
> > >> > Sorry, I didn't mean custom for import/export, but custom/private
> > >> module.
> > >> >
> > >> > What does ITP mean?
> > >>
> > >> You found the answer already.
> > >>
> > >> > > > The method I was using is simply running the following inside my
> > >> > > repository:
> > >> > > >
> > >> > > > >sudo python setup.py install
> > >> > >
> > >> > > Just out of interest: does it work? Usually Debian packages and
> local
> > >> > > Python
> > >> > > packages should be able to coexist. I tested this some time ago,
> but
> > >> would
> > >> > > like
> > >> > > to know, if you can confirm that.
> > >> >
> > >> >
> > >> > I just tried it. It installed properly but when I open the database
> in
> > >> the
> > >> > tryton client and try to open the list of module I get the following
> > >> error:
> > >> >
> > >> > OError: File not found :
> /dist-packages/trytond/modules/mail/tryton.cfg
> > >> >
> > >> > Not sure what is happening here.
> > >>
> > >> Apparently there is no tryton.cfg in your custom module. This file is
> > >> required
> > >> and must depend at least from ir.
> > >>
> > >>
> > > I don't think that this is the problem. I think that my module and its
> > > dependencies did not get installed in the correct folder where Tryton
> > > expects modules to be.
> > >
> >
> > This is definitely the problem. Setuptools is installing the modules at
> > /usr/local/lib/python2.7/dist-packages, but tryton looks at
> > /usr/lib/python2.7/dist-packages.
>

Just to set the record straight. This is not the issue at all. The issue
was that I had not restarted the tryton server like I thought...


-- 
*Vincent Bastos*
*Lava Lab Software*