I'm pleased to announce the release of feedparser 5.1.1!
This release contains a number of important changes that range from fixed crasher bugs to improved date and time string parsing. There are also some bug fixes that affect how various elements are parsed.
Unit test fixes
Several Linux distribution maintainers came forward after the last release and pointed out issues that ranged from missing unit test files to failures that only seemed to occur on x64 platforms. I believe all of the issues have been ironed out in this release, so feedparser 5.1.1 shouldn't pose a problem to include in package repositories.
This release contains a couple of changes to how certain elements are parsed.
itunes:keywords element is now split on commas, not whitespace. This brings feedparser in line with the element's description on Apple's website.
pubDate now maps to
published rather than
updated in the dictionary that feedparser returns. By mapping
published, its semantic meaning is retained, but developers may need to modify their software if they're only checking the
updated key. One software developer already pointed out that old versions of his software will be affected by this change, so a temporary fix is in place to give developers time to change their software:
updated does not exist, membership tests will always return False.
updated does not exist, and
published does exist, and
if the software accesses
feedparser will return the contents of
Here's an example:
>>> from feedparser import FeedParserDict >>> d = FeedParserDict(published='pub') >>> 'updated' in d False >>> d['updated'] 'pub' >>> d = FeedParserDict(published='pub', updated='today') >>> 'updated' in d True >>> d['updated'] 'today'
Remember that this is only a stopgap measure. It's intended to help avoid affecting users, should they be using an old version of some software with a new version of feedparser. This hack will be removed in a future version of feedparser.
A big thank you to everyone who contributed to this release! As always, if you find an issue don't hesitate to file a report on the issue tracker.