Éric Araujo <mer...@netwok.org> added the comment: Hello
This is indeed a problem with f2py. Please tell its maintaines that they can’t name an object “as” since it’s a reserved keyword in Python 2.6 and higher. Testing with 2.5 (previous stable version, released in 2006) would have shown it: <http://www.python.org/doc/2.5/whatsnew/pep-343.html> points to <http://www.python.org/dev/peps/pep-0343/> which tells in “Transition Plan”: “In Python 2.5, the new syntax will only be recognized if a future statement is present: from __future__ import with_statement This will make both 'with' and 'as' keywords. Without the future statement, using 'with' or 'as' as an identifier will cause a Warning to be issued to stderr. In Python 2.6, the new syntax will always be recognized; 'with' and 'as' are always keywords.” So we’ll close here, since it is a normal, documented behavior. The f2py people have to fix their code. Regards ---------- nosy: +merwok _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8031> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
