[issue13610] On Python parsing numbers.

2016-05-02 Thread Vladimir Rutsky
Changes by Vladimir Rutsky : -- nosy: +rutsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue13610] On Python parsing numbers.

2011-12-17 Thread Ezio Melotti
Ezio Melotti added the comment: I'll close this then. -- resolution: -> wont fix stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue13610] On Python parsing numbers.

2011-12-17 Thread Jean-Michel Fauth
Jean-Michel Fauth added the comment: > Ezio Melotti Good catch. I'm not complaining. I just find funny to see the number of editors not "colorizing" this kind of Python valid expressions. (IDLE included) For me, subject close. -- ___ Python tracker

[issue13610] On Python parsing numbers.

2011-12-17 Thread Raymond Hettinger
Raymond Hettinger added the comment: -1 I'm with Mark, Georg, and Benjamin on this one. -- nosy: +rhettinger ___ Python tracker ___ _

[issue13610] On Python parsing numbers.

2011-12-17 Thread Ezio Melotti
Ezio Melotti added the comment: >>> 999if 888else 888 File "", line 1 999if 888else 888 ^ SyntaxError: invalid token This might be because 888e5 is a valid expression, so the 'e' is parsed as part of the number rather than a separate token. >>> 999 if 888.else 888 File ""

[issue13610] On Python parsing numbers.

2011-12-17 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +gvanrossum versions: +Python 3.3 -Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue13610] On Python parsing numbers.

2011-12-17 Thread Jean-Michel Fauth
Jean-Michel Fauth added the comment: I have done a little bit hd/files archeology and found some of my comments. Pointing on number litterals is probably wrong. The fact is that, this happens with practically any expression. And strangely, not all keywords (constructs?) are affected. >>> 999i

[issue13610] On Python parsing numbers.

2011-12-17 Thread Georg Brandl
Georg Brandl added the comment: I don't see a good reason to change this. -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bu

[issue13610] On Python parsing numbers.

2011-12-16 Thread Terry J. Reedy
Terry J. Reedy added the comment: The proposal is to change the definition of numbers literals from X to one that is context-sensitive: X followed by whitespace or a syntactic symbol but not anything else, in particular, not by an identifier_start character. I am +-0 at the moment. > 1 and@

[issue13610] On Python parsing numbers.

2011-12-16 Thread Jesús Cea Avión
Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue13610] On Python parsing numbers.

2011-12-16 Thread Benjamin Peterson
Benjamin Peterson added the comment: I think it's fairly harmless. Perhaps Python 4. -- priority: normal -> low ___ Python tracker ___ __

[issue13610] On Python parsing numbers.

2011-12-16 Thread Mark Dickinson
Mark Dickinson added the comment: > Can this be fixed? Not without breaking backwards compatibility, I would think. -- nosy: +mark.dickinson ___ Python tracker ___

[issue13610] On Python parsing numbers.

2011-12-16 Thread Charles-François Natali
Charles-François Natali added the comment: > Can this be fixed? More or less. The following patch does the trick, but is not really elegant: """ --- a/Parser/tokenizer.c2011-06-01 02:39:38.0 + +++ b/Parser/tokenizer.c2011-12-16 08:48:45.0 + @@ -1574,6 +15

[issue13610] On Python parsing numbers.

2011-12-15 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue13610] On Python parsing numbers.

2011-12-15 Thread Jean-Michel Fauth
New submission from Jean-Michel Fauth : Can this be fixed? As far as I can remember (ver. 1.5.6), it has always existed. Python does not crash, I find it inelegant. Should it not be a SyntaxError? Side effect. Searching for keywords, (eg. with re, "\b") may practically always implies to handle t