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 Jim.Jewett
Recipients Jim.Jewett
Date 2012-01-19.20:52:36
SpamBayes Score 1.3530442e-08
Marked as misclassified No
Message-id <1327006357.41.0.958836774052.issue13832@psf.upfronthosting.co.za>
In-reply-to
Content
Parser/parsetok.c was recently changed (e.g. http://hg.python.org/cpython/rev/2bd7f40108b4 ) to raise an error if multiple statements were found in a single-statement compile call.  It sensibly ignores trailing whitespace and comments.  Unfortunately,

(1)  It looks only at (c == ' ' || c == '\t' || c == '\n' || c == '\014') as opposed to using Py_UNICODE_ISSPACE(ch)
(2)  It assumes that a "#" means the rest of the line is OK, instead of looking for additional linebreaks.

Not sure whether to mark this a bug or an enhancement, since it is already strictly better than the 3.2 behavior of never warning about extra text.
History
Date User Action Args
2012-01-19 20:52:37Jim.Jewettsetrecipients: + Jim.Jewett
2012-01-19 20:52:37Jim.Jewettsetmessageid: <1327006357.41.0.958836774052.issue13832@psf.upfronthosting.co.za>
2012-01-19 20:52:36Jim.Jewettlinkissue13832 messages
2012-01-19 20:52:36Jim.Jewettcreate