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 ? 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 -- Pierre-Louis
