On May 23, 6:39 pm, "Gabriel Genellina"
wrote:
> En Sat, 23 May 2009 12:32:24 -0300, LittleGrasshopper
> escribió:
>
>
>
> > On May 22, 12:42 am, "Gabriel Genellina"
> > wrote:
> >> En Wed, 20 May 2009 20:18:02 -0300, LittleGrasshopper
> >> escribió:
>
> >> > It appears that either absolute
En Sat, 23 May 2009 12:32:24 -0300, LittleGrasshopper
escribió:
On May 22, 12:42 am, "Gabriel Genellina"
wrote:
En Wed, 20 May 2009 20:18:02 -0300, LittleGrasshopper
escribió:
> It appears that either absolute imports (or my brain) aren't working.
> Given a module string.py which is in
On May 22, 12:42 am, "Gabriel Genellina"
wrote:
> En Wed, 20 May 2009 20:18:02 -0300, LittleGrasshopper
> escribió:
>
> > New to the group, this is my first post...
>
> > It appears that either absolute imports (or my brain) aren't working.
> > Given a module string.py which is in the same dire
En Wed, 20 May 2009 20:18:02 -0300, LittleGrasshopper
escribió:
New to the group, this is my first post...
It appears that either absolute imports (or my brain) aren't working.
Given a module string.py which is in the same directory as a.py:
#File a.py
from __future__ import absolute_import
On May 20, 4:18 pm, LittleGrasshopper wrote:
> New to the group, this is my first post...
>
> It appears that either absolute imports (or my brain) aren't working.
> Given a module string.py which is in the same directory as a.py:
>
> #File a.py
> from __future__ import absolute_import
>
> import
New to the group, this is my first post...
It appears that either absolute imports (or my brain) aren't working.
Given a module string.py which is in the same directory as a.py:
#File a.py
from __future__ import absolute_import
import string
print string # Module imported is string.py in curren
