On 16/08/10 15:26 +0200, Paul J Stevens wrote: > > Hi all, > > Has there ever been any discussion of making trytond.modules a namespace > package? > > I'm working in a virtualenv/buildout setting where all modules are > checked out outside the trytond.modules directory. > > i.e: > > tryton.buildout/ > src/ > trytond/ > account/ > party/ > calendar/ > ... > > there are several reasons for /not/ installing inside trytond.modules > but mostly I like the modular nature of tryton and prefer to leverage it > - installing inside trytond/modules/ just seems so not-pythonic.
Could you explain why? > This approach works really well, until I noticed some exceptions in the > log related to dateutil. Turns out we have a namespace conflict between > the core calendar.py and the tryton module with the same name (entry-point). Why not using the real name of the package: trytond_account, trytond_party etc. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpMYB3TZ5mx5.pgp
Description: PGP signature
