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 mgedmin
Recipients mgedmin
Date 2014-02-12.14:07:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392214076.98.0.911994871276.issue20608@psf.upfronthosting.co.za>
In-reply-to
Content
I was looking at the current hg tip.  The lexer emits E_TOKEN errors for the following cases:
- invalid hex digit
- invalid octal digit
- invalid binary digit
- invalid digit in float exponent
- old-style octal constant (e.g. 001), which is no longer accepted

I think I can come up with a patch that replaces them all with different error codes (E_BAD_HEX_DIGIT etc.) and different error messages.  Does that sound like an acceptable change?  (I never contributed non-documentation patches to CPython before.)
History
Date User Action Args
2014-02-12 14:07:57mgedminsetrecipients: + mgedmin
2014-02-12 14:07:56mgedminsetmessageid: <1392214076.98.0.911994871276.issue20608@psf.upfronthosting.co.za>
2014-02-12 14:07:56mgedminlinkissue20608 messages
2014-02-12 14:07:56mgedmincreate