[Python-Dev] Bug in from __future__ processing?
Martin Maly
Martin.Maly at microsoft.com
Sat Mar 4 04:39:11 CET 2006
More information about the Python-Dev mailing list
Sat Mar 4 04:39:11 CET 2006
- Previous message: [Python-Dev] FrOSCon 2006 - Call for {Papers|Projects}
- Next message: [Python-Dev] Bug in from __future__ processing?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [Python-Dev] FrOSCon 2006 - Call for {Papers|Projects}
- Next message: [Python-Dev] Bug in from __future__ processing?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list