From 737fb89dd15e4db6ef30d25963e774ae09cc49dc Mon Sep 17 00:00:00 2001 From: Andrew Svetlov Date: Tue, 18 Dec 2012 21:14:22 +0200 Subject: Issue #16714: use 'raise' exceptions, don't 'throw'. Patch by Serhiy Storchaka. --- Lib/email/feedparser.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'Lib/email/feedparser.py') diff --git a/Lib/email/feedparser.py b/Lib/email/feedparser.py index aa8a2ffa644..16ed2885d71 100644 --- a/Lib/email/feedparser.py +++ b/Lib/email/feedparser.py @@ -13,7 +13,7 @@ parser. It returns when there's nothing more it can do with the available data. When you have no more data to push into the parser, call .close(). This completes the parsing and returns the root message object. -The other advantage of this parser is that it will never throw a parsing +The other advantage of this parser is that it will never raise a parsing exception. Instead, when it finds something unexpected, it adds a 'defect' to the current message. Defects are just instances that live on the message object's .defects attribute. @@ -214,7 +214,7 @@ class FeedParser: # supposed to see in the body of the message. self._parse_headers(headers) # Headers-only parsing is a backwards compatibility hack, which was - # necessary in the older parser, which could throw errors. All + # necessary in the older parser, which could raise errors. All # remaining lines in the input are thrown into the message body. if self._headersonly: lines = [] -- cgit v1.2.3