from future import scope problem

mykhal michal.bozon at gmail.com
Fri Mar 13 02:58:23 CET 2009


On Mar 13, 12:46 am, Terry Reedy <tjre... at udel.edu> wrote:
> mykhal wrote:
> > hi,
> > importing from __future__ seems to have no effect when invoked in
> > local scope using exec statement.
> > I supposed
>
> > g = {}
> > exec 'from __future__ import division' in g
> > eval('1/2', g)
>
> > should yield 0.5, but it yields 0.
>
> > is it OK, or a bug?
>
> Please to read the fine manual.
>
> tjr
>
> ps.
>
> " future statement must appear near the top of the module. The only
> lines that can appear before a future statement are:
>
> the module docstring (if any),
> comments,
> blank lines, and
> other future statements.
> "

as you can see, my future import statement is the very first code of
the virtual module, using g dictionary as its globals. i know, it can
be barely called module..
if it produced SyntaxError in this exec/in usage as well, I'd have no
questions.



More information about the Python-list mailing list