* W. Trevor King <[email protected]> [140924 11:20]: > On Tue, Sep 09, 2014 at 09:13:57AM -0700, W. Trevor King wrote: > > On Tue, Sep 09, 2014 at 10:58:53AM -0400, Joey Hess wrote: > > > Perhaps if it's not a fatal problem it should not display as an > > > "error"? > > > > I problably should have done this a while ago. It's in master now [1]. > > Actually, I'm going to claw that back, since we don't want things like > #760078 slipping by as warnings. Maybe I should change 'processing > error' to 'feedparser bozo'?
The code already does a big switch depending on exc's class. IMHO it's best to add an extra case to display a warning if exc is a NonXMLContentType exception (like the case just above for CharacterEncodingOverride), and to keep the existing behaviour (log an error) for other exception classes, which will catch stuff like #760078. I'll send you a patch if this sounds good to you. Cheers -- Etienne Millon -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
