How should multiple (related) projects be arranged (structured) and configured so that they can share code, have a related package structure and enable proper unittesting, and ensuring no namespace collisions
Peter Otten
__peter__ at web.de
Fri Apr 21 02:47:29 EDT 2006
ToddLMorgan at gmail.com wrote:
> ie does the first instance of the package a.b.c effectively mask out
> the others so that if a.b.c.common occurs first in the PYTHONPATH then
> a.b.c.project1 will never be found as the "a.b.c" package is only
> loaded from the a.b.c.common folder?
By default, yes. But there's a way around this limitation:
http://docs.python.org/lib/module-pkgutil.html
Peter
More information about the Python-list
mailing list