A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2001-February/013242.html below:

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

[Python-Dev] one more restriction for from __future__ import ... [Python-Dev] one more restriction for from __future__ import ...Samuele Pedroni Samuele Pedroni <pedroni@inf.ethz.ch>
Tue, 27 Feb 2001 22:54:43 +0100 (MET)
Hi.

> >    In addition, all future_statments 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.
> >    + Other future_statements.
> 
> 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
Will the error be unclear for the user or there's another problem?

In jython I get from parser an abstract syntax tree, so it is difficult
to distringuish the ; from true newlines ;)

regards, Samuele




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4