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.
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).
This problem does /not/ occur in the 1.6.0 eggs released, so it's not
critical in any way. But to me it seems an indication of what may become
a more urgent matter as adoption of tryton accelerates.
Same issue let to a plethora of namespaces in the plone community, with
plenty of pros and cons [1]. That's why I suggest making just
trytond.modules a separate namespace [2].
[1] http://weblion.psu.edu/news/are-we-overusing-namespace-packages
[2] http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages
kind regards,
--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
--
[email protected] mailing list
