feedparser
feedparser copied to clipboard
Parse feeds in Python
When going to [this feed](https://www.unodc.org/unodc/en/feed/publications.xml?ref=fp), the `published` field is populated as the date twice in a row (`u'2016-05-24 14:17:57.02016-05-24 14:17:57.0'`). ``` xml UNODC Publicationshttp://www.unodc.org/unodc/en/feed/publications.xmlUNODC PublicationsWorld wildlife crime report 2016http://www.unodc.org/documents/data-and-analysis/wildlife/World_Wildlife_Crime_Report_2016_final.pdfhttp://www.unodc.org/documents/data-and-analysis/wildlife/World_Wildlife_Crime_Report_2016_final.pdfTue, 24...
Would it be possible to add the [opensearch namespace](http://www.opensearch.org/Specifications/OpenSearch/1.1)? I don't know where this would go now (or I'd have written a patch) but in the monolithic version, the namespace...
Hello again and thanks for the great work. Unless I missed something, I think there is no way to tell Feedparser the feed encoding if we already know it. In...
The handling of the media:description element in 5.2.1 ends up overwriting the 'content' field of an item. This seems like a particular case of issue #35. An example feed item...
According to [RSS 2.0 Specification](http://cyber.law.harvard.edu/rss/rss.html#ltcategorygtSubelementOfLtitemgt), _category_ item may include multiple values. ``` You may include as many category elements as you need to, for different domains, and to have an...
This is a design change that I think would be a positive move for feedparser. It is somewhat related to #24 but isn't exactly the same. Right now, if feedparser...
"Confident" means "metadata of the document explicitly indicates that the encoding is UTF-8". ## Background of the patch When a UTF-8 feed has a few invalid characters but the rest...
Bumps [jinja2](https://github.com/pallets/jinja) from 3.1.2 to 3.1.3. Release notes Sourced from jinja2's releases. 3.1.3 This is a fix release for the 3.1.x feature branch. Fix for GHSA-h5c8-rqwp-cp95. You are affected if...
Using version 6.0.11 and Python 3.12 The docs for `parse()` say ``` ...snip... Wrap an untrusted string in a :class:`io.StringIO` or :class:`io.BytesIO` to avoid this. Do not pass untrusted strings...
Add testcase to capture the issue from #297 and parts of #301. If someone can point me to where this should be fixed i will take a stab at it...