[Python-Dev] one more restriction for from __future__ import ...

[Guido van Rossum]

> I would like to add another restriction:
> 
>     A future_statement must appear on a line by itself.  It is not
>     legal to combine a future_statement without any other statement
>     using a semicolon.
> 
> It would be a bear to implement error handling for cases like this:
> 
> from __future__ import a; import b; from __future__ import c

Really?!?  Why?  Isn't it straightforward to check that everything you
encounter in a left-to-right leaf scan of the parse tree is either a
future statement or a docstring until you encounter a non-future?

--Guido van Rossum (home page: http://www.python.org/~guido/)