Also, as a bonus this would come with the possibility to install modules inside the tryton data path, with tryton user rights. This would allow to have a module to install modules from the internet... Am 04.09.2014 08:09 schrieb "Simon Klemenc" <simon.klem...@gmail.com>:
> > Am 04.09.2014 02:19 schrieb "Pierre-Louis Bonicoli" < > pierre-louis.bonic...@gmx.fr>: > > > > On 04/09/2014 01:04, Simon Klemenc wrote: > > > You are right, this is more of a first-world-problem. Its absolutely > > > doable to add a setup.py from the template in hg but when doing only > > > slight modifications to the view, workflow, models,... or splitting > > > modules it makes life easier to just work inside a dedicated directory, > > > and have trytond behave more like a framework... > > > > Is your goal to use a Tryton module located outside the > > "trytond/modules" directory ? > > Yes, the goal is to be able to manage the large number of modules in a > freely defined folder-structure: custom, tryton, 3rd-party maybe, and to > have it working like an encapsulated "app"... > > >If so you could use symbolic links or > > setup.py: > > > > 1. Register (Python) the module using setup.py: inside the source > > directory of the module (if this is a custom module, use a setup.py of a > > standard module as example): > > $ PYTHONPATH=/tmp/custom/lib/python2.7/site-packages python setup.py \ > > develop --prefix /tmp/custom > > > > 2. Install the module > > $ PYTHONPATH=/tmp/custom/lib/python2.7/site-packages trytond \ > > -d db -i name > > > > Thanks, i will try to add to my pythonpath in the evening and check if > thats convenient for me... > > Simon >
