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 gvanrossum
Recipients alex, glyph, gvanrossum, ncoghlan
Date 2014-06-05.16:15:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401984930.71.0.674405173478.issue21669@psf.upfronthosting.co.za>
In-reply-to
Content
I'm sorry, but I find this way too intrusive, and a little risky too (I'm not sure how to verify even that the new parser accepts exactly the same set of programs as the old version).

I would much prefer a solution to this particular issue along the lines of a heuristic based on detecting whether the line where the syntax error occurs starts with the token 'print' or 'exec' followed by anything except a left parenthesis.

Such a heuristic could also be added to 3.4.
History
Date User Action Args
2014-06-05 16:15:30gvanrossumsetrecipients: + gvanrossum, ncoghlan, glyph, alex
2014-06-05 16:15:30gvanrossumsetmessageid: <1401984930.71.0.674405173478.issue21669@psf.upfronthosting.co.za>
2014-06-05 16:15:30gvanrossumlinkissue21669 messages
2014-06-05 16:15:30gvanrossumcreate