Relative Imports, why the hell is it so hard?
pavlovevidence at gmail.com
Wed Mar 25 05:56:49 CET 2009
On Mar 24, 8:32 pm, Istvan Albert <istvan.alb... at gmail.com> wrote:
> On Mar 24, 9:35 pm, Maxim Khitrov <mkhit... at gmail.com> wrote:
> > Works perfectly fine with relative imports.
> This only demonstrates that you are not aware of what the problem
> actually is.
> Try using relative imports so that it works when you import the module
> itself. Now run the module as a program. The same module that worked
> fine when you imported it will raise the exception:
PEP 366 addresses this issue.
Not the best solution, one that still involves boilerplate, but it is
much less of a hack than your version, and at least it has the
blessing of the language designers so it won't unceremoniously break
at some point.
More information about the Python-list