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 steve.dower
Recipients Joshua.Landau, benjamin.peterson, loewis, python-dev, steve.dower, wim.glenn
Date 2015-04-15.15:24:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
FTR, I think this was a bad fix and we should have just changed the spec to require a space between numeric literals and identifiers.

Closing as by design would have been fine in my opinion as well, since the spec says spaces are required when it's ambiguous, and this case looks fairly ambiguous. There's also a bit of a slippery slope here where we now have to fix "0x1and 3" or be very explicit about why it is different.

I haven't even mentioned changing the parser in a dot release. That seems somewhat ridiculous.

Everyone else who writes a Python parser (all the IDEs and type checkers, other implementations, etc.) would prefer it if we didn't need our tokenisers to look ahead two characters.
Date User Action Args
2015-04-15 15:24:10steve.dowersetrecipients: + steve.dower, loewis, benjamin.peterson, python-dev, Joshua.Landau, wim.glenn
2015-04-15 15:24:10steve.dowersetmessageid: <>
2015-04-15 15:24:10steve.dowerlinkissue21642 messages
2015-04-15 15:24:10steve.dowercreate