A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-March/062047.html below:

[Python-Dev] Bug in from __future__ processing?

[Python-Dev] Bug in from __future__ processing? [Python-Dev] Bug in from __future__ processing?Martin Maly Martin.Maly at microsoft.com
Sat Mar 4 04:39:11 CET 2006
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, don't raise Syntax error in Python 2.4.2. Is it a bug?

I am asking whether in IronPython we should try to match behavior of Python compiler, or stick to the language spec. In this case, I believe that we should stick to the spec and report a bug in Python compiler.

Thanks
Martin

Example 1:
------------------
x = 10 / 2
from __future__ import division
------------------


Example 2:
------------------
from sys import *
from __future__ import division
------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20060303/8f1905c8/attachment.htm 
More information about the Python-Dev mailing list

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