A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-September/049137.html below:

[Python-Dev] Odd compile errors for bad genexps

[Python-Dev] Odd compile errors for bad genexps [Python-Dev] Odd compile errors for bad genexpsTim Peters tim.peters at gmail.com
Thu Sep 30 04:58:38 CEST 2004
[Raymond Hettinger]
> Okay, those two are fixed.

Thank you!

>> 2. Why didn't it echo the offending line?

> The code for com_error() screens out the line numbering when in the
> interactive mode.  You get the full echo when running a script.
> 
> What is interesting is that some syntax errors ("2 & * 3" for example)
> by-pass com_error() and echo the line with a caret pointing at the
> offending token.

Or plain "+" or plain "if" or "2 &" or "*3" or "from math import sin
as" etc etc.  That's why I asked.  I almost always see an echo echo
echo.  But those are actually syntax errors, in the sense that can't
be derived from the formal grammar.

> These are both probably as they should be.

Not if it makes life harder for doctest <wink>.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4