Robert Kern wrote:
> Remember that this is code in the A.B.C module.
Oh! That clears it all up! I wasn't realizing that the import statements
were being executed from within the C module! Thanks! :)
--
http://mail.python.org/mailman/listinfo/python-list
John Salerno wrote:
> Robert Kern wrote:
>
>> What is ambiguous about A.B.D, A.E, and A.F.G? But if you like:
>
> I guess maybe I was looking at it backwards. From the way it was worded,
> I thought the only information we had to use was the structure A.B.C,
> and then given a statement like:
>
John Salerno wrote:
> Robert Kern wrote:
>
> > What is ambiguous about A.B.D, A.E, and A.F.G? But if you like:
>
> I guess maybe I was looking at it backwards. From the way it was worded,
> I thought the only information we had to use was the structure A.B.C,
> and then given a statement like:
>
>
Robert Kern wrote:
> What is ambiguous about A.B.D, A.E, and A.F.G? But if you like:
I guess maybe I was looking at it backwards. From the way it was worded,
I thought the only information we had to use was the structure A.B.C,
and then given a statement like:
from . import D
we just had to f
John Salerno wrote:
> I'm reading the "What's New" section of the 2.5 docs, and I'm a little
> confused by the last section of "Absolute and Relative Imports":
>
> ---
> For example, code in the A.B.C module can do:
>
> from . import D
I'm reading the "What's New" section of the 2.5 docs, and I'm a little
confused by the last section of "Absolute and Relative Imports":
---
For example, code in the A.B.C module can do:
from . import D # Imports A.B.D
from .. import E
