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/049136.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 genexpsRaymond Hettinger python at rcn.com
Thu Sep 30 02:40:42 CEST 2004
> [Tim]
> > >>> (i for i in x) = 2
> > SystemError: assign to generator expression not possible
> >
> > 1. Why is that a SystemError instead of a SyntaxError?  SystemError
> >    doesn't make sense.
 . . .
> > >>> (i for i in x) += 2
> > SyntaxError: augmented assign to tuple literal not possible
> >
> > 3. That's not a tuple literal

Okay, those two are fixed.



> > 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.

These are both probably as they should be.



Raymond 

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