[Python-Dev] relative import circular problem (original) (raw)

Eric Snow ericsnowcurrently at gmail.com
Thu Apr 4 06:57:15 CEST 2013

On Mon, Apr 1, 2013 at 4:52 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:

This is really a quality-of-implementation issue in the import system rather than a core language design problem. It's just that those of us with the knowledge and ability to fix it aren't inclined to do so because circular imports usually (although not quite always) indicate a need to factor some common code out into a third support module imported by both of the original modules. At that point, the code is cleaner and more decoupled, and the uneven circular import support ceases to be a problem for that application.

+1

-eric

More information about the Python-Dev mailing list