On 3/4/06, Anthony Baxter [EMAIL PROTECTED] wrote:
On Saturday 04 March 2006 15:34, Tim Peters wrote:
Indeed! But whose arm could we twist to get them to repair the
compiler in 2.4? I'd settle for a blurb in the next 2.4 NEWS just
noting that 2.5 will follow the documented syntax. That
Guido van Rossum wrote:
I don't think a change like this should go into a 2.4.x release. It
stands a very very high chance of breaking someone's code. I _could_
be convinced about a warning being emitted about it, though I'm not
going to have the time to figure out the new compiler to do
On Saturday 04 March 2006 15:34, Tim Peters wrote:
Indeed! But whose arm could we twist to get them to repair the
compiler in 2.4? I'd settle for a blurb in the next 2.4 NEWS just
noting that 2.5 will follow the documented syntax. That may even
be desirable, to avoid breaking working
Hello,
The Python spec states that the from
__future__ import statement can only occur at the beginning of
the file, preceded only by doc strings, comments, empty lines or other future
statements. The following code snippets, however, dont raise Syntax
error in Python 2.4.2. Is it a
[Martin Maly]
The Python spec states that the from __future__ import … statement can
only occur at the beginning of the file, preceded only by doc strings,
comments, empty lines or other future statements. The following code
snippets, however, don't raise Syntax error in Python 2.4.2. Is it a
On 3/3/06, Tim Peters [EMAIL PROTECTED] wrote:
[Martin Maly]
The Python spec states that the from __future__ import … statement can
only occur at the beginning of the file, preceded only by doc strings,
comments, empty lines or other future statements. The following code
snippets,
[Tim]
Doesn't look like Guido responded, so I'll channel him and declare
that he intended to agree with me after all ;-)
[Guido]
It was so obvious that you were right I didn't bother to agree at the
time. But yes, I agree.
Of course you do. It was obvious to you, and therefore-- as your
