This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients PeterJones, benjamin.peterson, eric.araujo
Date 2010-03-01.03:12:53
SpamBayes Score 8.743699e-05
Marked as misclassified No
Message-id <1267413175.97.0.512449595883.issue8031@psf.upfronthosting.co.za>
In-reply-to
Content
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
History
Date User Action Args
2010-03-01 03:12:56eric.araujosetrecipients: + eric.araujo, benjamin.peterson, PeterJones
2010-03-01 03:12:55eric.araujosetmessageid: <1267413175.97.0.512449595883.issue8031@psf.upfronthosting.co.za>
2010-03-01 03:12:54eric.araujolinkissue8031 messages
2010-03-01 03:12:53eric.araujocreate