[Python-ideas] Re: Improve SyntaxError for obvious issue:

2020-01-15 Thread Barry Scott
> On 14 Jan 2020, at 18:42, Guido van Rossum wrote: > > On the subject of replacing the current parser, I am actively working on > that. See GitHub.com/gvanrossum/pegen. Will that allow me to write this? if a > 3 and x < 6: doit() Barry > > On Tue, Jan 14, 2020 at 10:32 Andrew

[Python-ideas] Re: Improve SyntaxError for obvious issue:

2020-01-14 Thread David Mertz
For what it's worth, after 20+ years of using Python, forgetting the colon for blocks remains the most common error I make by a fairly wide margin. Of course, once I see the error message—even being not all that descriptive of the real issue—I immediately know what to fix too. On Tue, Jan 14,

[Python-ideas] Re: Improve SyntaxError for obvious issue:

2020-01-14 Thread Naomi Ceder
My pleasure! Glad to see you have discussed with André! On Tue, 14 Jan 2020 at 13:52, Ntentos Stavros wrote: > For the sake of completeness: friendly-traceback is already handling > this. @Naomi Thank you for bringing this up :-) > > https://github.com/aroberge/friendly-traceback/issues/42 > --

[Python-ideas] Re: Improve SyntaxError for obvious issue:

2020-01-14 Thread Ntentos Stavros
For the sake of completeness: friendly-traceback is already handling this. @Naomi Thank you for bringing this up :-) https://github.com/aroberge/friendly-traceback/issues/42 -- Yours faithfully, Ntentos Stavros ___ Python-ideas mailing list --

[Python-ideas] Re: Improve SyntaxError for obvious issue:

2020-01-14 Thread Σταύρος Ντέντος
On Tue, 14 Jan 2020 at 20:43, Guido van Rossum wrote: > > On the subject of replacing the current parser, I am actively working on > that. See GitHub.com/gvanrossum/pegen. Sounds interesting! I could open you a ticket, if something like that is not implemented / in your plans currently. > > On

[Python-ideas] Re: Improve SyntaxError for obvious issue:

2020-01-14 Thread Naomi Ceder
The friendly-traceback project (in early alpha) is working on making traceback messages more helpful and translatable - https://aroberge.github.io/friendly-traceback-docs/docs/html/ On Tue, 14 Jan 2020 at 12:43, Guido van Rossum wrote: > On the subject of replacing the current parser, I am

[Python-ideas] Re: Improve SyntaxError for obvious issue:

2020-01-14 Thread Guido van Rossum
On the subject of replacing the current parser, I am actively working on that. See GitHub.com/gvanrossum/pegen. On Tue, Jan 14, 2020 at 10:32 Andrew Barnert via Python-ideas < python-ideas@python.org> wrote: > On Jan 14, 2020, at 05:22, Σταύρος Ντέντος wrote: > > > > Hello there, > > > > If I

[Python-ideas] Re: Improve SyntaxError for obvious issue:

2020-01-14 Thread Andrew Barnert via Python-ideas
On Jan 14, 2020, at 05:22, Σταύρος Ντέντος wrote: > > Hello there, > > If I have simply missed a double colon starting a for loop > > File "./bbq.py", line 160 >for config_file in config_files > ^ > SyntaxError: invalid syntax > > the message is not as