Message21666
| Author |
tim.peters |
| Recipients |
| Date |
2004年11月16日.02:03:42 |
| SpamBayes Score |
| Marked as misclassified |
| Message-id |
| In-reply-to |
| Content |
Logged In: YES
user_id=31435
Nick, the semantics of circular imports aren't clear even if no
packages are involved. Note that the Reference manual is
silent about such cases. In effect, it's defined by the
implementation, and some people think they know how that
works -- although nobody has credibly claimed to fully
understand the implementation consequences since Gordon
McMillan vanished <0.5 wink>.
While I expect this bug report to sit here for years (it's hard
to imagine anyone caring enough to devote the time needed
to untangle this subsystem), I'll note in passing that this
case "works" if bar.py uses relative import instead; i.e., if it
begins with
import baz
y = baz.y
instead of with
import eek.foo.baz
y = eek.foo.baz.y
Then it stops referencing attributes that don't exist before
the whole chain of imports completes. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2007年08月23日 14:23:49 | admin | link | issue992389 messages |
| 2007年08月23日 14:23:49 | admin | create |
|