Message 132063 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	Trundle
Recipients	Trundle, loewis, marienz, terry.reedy
Date	2011年03月25日.01:05:27
SpamBayes Score	2.104756e-06
Marked as misclassified	No
Message-id	<AANLkTinTQzEedrsHGe_ok0yqUWy6j8TxsQU8bUn_S1W3@mail.gmail.com>
In-reply-to	<1299274211.29.0.177006727238.issue11343@psf.upfronthosting.co.za>

Content
On Fri, Mar 4, 2011 at 9:30 PM, Terry J. Reedy <report@bugs.python.org> wrote: > I agree with Martin (from 2000) that SyntaxError is not right either. Perhaps a new ParseError subclass thereof. I added a new `ParserError` that inherits from `SyntaxError`. > I presume REPL == read-eval-print-loop (from Google). Would a new error help such programs (like code.interact, or IDLE)? Yes, I meant a read-eval-print-loop. A new error would help and if it's a subclass of SyntaxError, they most likely need no changes at all to handle that new error, as they have to deal with SyntaxErrors anyway.

Content

On Fri, Mar 4, 2011 at 9:30 PM, Terry J. Reedy <report@bugs.python.org> wrote:
> I agree with Martin (from 2000) that SyntaxError is not right either. Perhaps a new ParseError subclass thereof.
I added a new `ParserError` that inherits from `SyntaxError`.
> I presume REPL == read-eval-print-loop (from Google). Would a new error help such programs (like code.interact, or IDLE)?
Yes, I meant a read-eval-print-loop. A new error would help and if
it's a subclass of SyntaxError, they most likely need no changes at
all to handle that new error, as they have to deal with SyntaxErrors
anyway.

Files
File name	Uploaded
issue11343.patch	Trundle, 2011年03月25日.01:05:26

History
Date	User	Action	Args
2011年03月25日 01:05:29	Trundle	set	recipients: + Trundle, loewis, terry.reedy, marienz
2011年03月25日 01:05:27	Trundle	link	issue11343 messages
2011年03月25日 01:05:27	Trundle	create

homepage