[issue8031] Can't get f2py to work at all
report at bugs.python.org
Mon Mar 1 04:12:55 CET 2010
Éric Araujo <merwok at netwok.org> added the comment:
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.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list