Am 04.09.2014 00:17 schrieb "Cédric Krier" <cedric.kr...@b2ck.com>: > > On 03 Sep 23:56, Simon wrote: > > Am 03.09.2014 um 23:13 schrieb Cédric Krier: > > >On 03 Sep 11:11, Simon Klemenc wrote: > > >>On Tuesday, September 2, 2014 11:07:44 PM UTC+2, Cédric Krier wrote: > > >>>On 02 Sep 09:14, simon....@gmail.com <javascript:> wrote: > > >>>>hi there, > > >>>> > > >>>>first thing, im sorry for doing this in reverse order: i have already > > >>>>opened a codereview at http://codereview.tryton.org/10481002/ and am > > >>>now > > >>>>writing in here to state my motivation. > > >>>> > > >>>> > > >>>>the reason i even took a deeper look at modules/__init__.py was that i > > >>>>wanted to run tryton in a more project/framework oriented way: having a > > >>>>project folder with tryton modules and my own modules, similar to how a > > >>>>common django-project would look like. This would ease the process of > > >>>>developing (getting started using sqlite straight away) and creating > > >>>>docker-instances a lot for me. > > >>>This is a wrong goal and will not land in Tryton because: > > >>> > > >>> - it does enforce uniqueness of module name > > >>> > > >>Really, did you ever try to load more than one module with non-unique names? > > >>I doubt you would ever succeed on this for quite some reasons: [including > > >>links :) ] > > >It is by design! Directory names are *unique*. > > > > i cant follow your argumentation: > > why is it a "wrong goal" to enforce name-uniqueness first and "by design" > > later on? > > OK I was not clear. Currently by design module name is enforced to be > unique because of the single directory.
Ok thanks, so name-uniqueness is the desired behaviour.. this would not change with a key-value dictionary as a central registry like in the patch > > > >> - it is useless because modules can be registered via pkg_resources. > > >>True. > > >>but then i still have to add a setup.py and install using pip, which turns > > >>out to be not soo simple to automate with docker.. > > >Blame docker. > > > > thanks for that, truely inspiring!! > > If such simple task are not doable with docker who to blame? > Moreover, having a setup.py is *absolutly* not optional. 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... To my opinion it is indeed a very nice framework but to get started in developing is not as straightforward as with other frameworks (although it could be, easily) Have a nice evening, i appreciate the fast responses as i dont have so much time during the day.. Simon > > -- > Cédric Krier - B2CK SPRL > Email/Jabber: cedric.kr...@b2ck.com > Tel: +32 472 54 46 59 > Website: http://www.b2ck.com/
