[issue8031] Can't get f2py to work at all

Éric Araujo added the comment: While I’m thinking about this, is there a way to make the syntax error traceback more informative, i.e. adding “'{}' is a reserved keyword” in such cases? -- ___ Python tracker

[issue8031] Can't get f2py to work at all

Éric Araujo 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:

[issue8031] Can't get f2py to work at all

e clear in the documentation to not do what I did. Peter. - Original Message - From: "Peter Jones" To: Sent: Sunday, February 28, 2010 2:45 PM Subject: [issue8031] Can't get f2py to work at all New submission from Peter Jones : I am user 11943. OS is Windows Vista Ulti

[issue8031] Can't get f2py to work at all

Benjamin Peterson added the comment: This is a 3rd party package problem. Please ask the maintainers of it. -- nosy: +benjamin.peterson resolution: -> invalid status: open -> closed ___ Python tracker

[issue8031] Can't get f2py to work at all

New submission from Peter Jones : I am user 11943. OS is Windows Vista Ultimate. I have followed the instructions on how to use f2py and get this error when I try it (is this a known bug? It appears that there is bug in f2py): C:\Python26\Scripts>python f2py.py Traceback (most recent call last