RetroSearch Browse

Mon Apr 12 13:35:27 EDT 2004 · http://mail.python.org/pipermail/python-dev/2004-April/044201.html

On Mon, 2004-04-12 at 12:55, Aahz wrote:

> > I think they belong in every module.  A future statement is a compiler
> > gimmick and modules are compiled separately, so each module ought to
> > have its own future statement.  If not, the compiler (and human reader)
> > have no idea whether a future statement is in effect.  Obviously, the
> > compiler and the reader could learn about some change to import
> > semantics by studying context, but that's extra complexity I'd like to
> > avoid (particular in the case of the compiler).
> 
> That's what I expected the reaction to be from others.  Barry, if you
> want your change, lobby Guido.  ;-)

I might be crazy but I'm not insane. :)

-Barry

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2004-April/044201.html below:

[Python-Dev] Re: PEP 328 -- relative and multi-line import