[issue32982] Parse out invisible Unicode characters?

R. David Murray added the comment: I think it sounds like a good idea to put the printed representation as a repered string, followed by the code point representation in parenthesis, in that message after "invalid character". -- nosy: +r.david.murray _

[issue32982] Parse out invisible Unicode characters?

Glenn Linderman added the comment: Characters should not be stripped during compilation. But I can see where it might be helpful if the codepoint of the character, and the printed form just in case it is printable, could helpfully be included in the error message, as well as having the ^ poin

[issue32982] Parse out invisible Unicode characters?

Matthew Barnett added the comment: For the record, '\u200e' is '\N{LEFT-TO-RIGHT MARK}'. -- nosy: +mrabarnett ___ Python tracker ___ ___

[issue32982] Parse out invisible Unicode characters?

New submission from Franklin? Lee : The following line should have a character that trips up the compiler. ‎indices = range(5) The character is \u200e, and was inserted by Google Keep. (I've already reported the issue to Google as a regression.) Here's the error message: """ File "", line