Quixote uses an importing convention which looks like

from quixote.module import something

This breaks when quixote is a subpackage within a larger hierarchy, as
happens with python modules in at least one company.  Changing the
quixote imports to the new absolute (eg. from blah.blah.quixote.module
import something) breaks when __init__.py imports util.py which wants
to circularly import quixote/__init__.py.  Using absolute imports also
makes it impossible to have two versions of quixote installed without
sys.path hackery.

Changing all imports to relative imports fixes all these problems.  In
fact, http://www.python.org/doc/essays/packages.html, the closest
thing python has to documentation on packages (apparently no one has
updated the lang ref since 1.5), seems to recommend relative package
imports (see "Intra-package References").  It's not too clear though.

Any particular reason to not use relative imports in quixote?
_______________________________________________
Quixote-users mailing list
[email protected]
http://mail.mems-exchange.org/mailman/listinfo/quixote-users

Reply via email to