[Python-Dev] Odd compile errors for bad genexps

Tim 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