You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,10 +85,11 @@ You can also check out this nice [working implementation](https://github.com/scr
85
85
you should set the `feedurl` option. Otherwise, feel free to ignore this option.
86
86
87
87
-`resume_saxerror` - Set to `false` to override Feedparser's default behavior, which
88
-
is to emit any `SAXError` on `error` and then automatically resume parsing. In
88
+
is to silently handle them and then automatically resume parsing. In
89
89
my experience, `SAXErrors` are not usually fatal, so this is usually helpful
90
-
behavior. If you want total control over handling these errors and optionally
91
-
aborting parsing the feed, use this option.
90
+
behavior. If you prefer to abort parsing the feed when there's a `SAXError`,
91
+
set `resume_saxerror` to `false`, which will cause the `SAXError` to be emitted
92
+
on `error` and abort parsing.
92
93
93
94
## Examples
94
95
@@ -104,7 +105,7 @@ Each readable chunk is an object representing an article in the feed.
104
105
### Events Emitted
105
106
106
107
*`meta` - called with feed `meta` when it has been parsed
107
-
*`error` - called with `error` whenever there is a Feedparser error of any kind (SAXError, Feedparser error, etc.)
108
+
*`error` - called with `error` whenever there is a fatal Feedparser error. SAXErrors are only emitted here when `resume_saxerror` is `false`; otherwise they are silently collected in `feedparser.errors`.
108
109
109
110
## What is the parsed output produced by feedparser?
0 commit comments