kurtmckee / listparser Goto Github PK

listparser only exposes feed.title. It will be the text attribute of an outline, or, if unavailable, the title attribute.

However, OPML 2.0 marks the text attribute as mandatory.

As a result, if an RSS reader adheres OPML 2.0, the exported OPML may have both tilte and text even if there is no user-defined feed title.

I propose that listparser exposes feed.title (keep the current behavior), feed.title_orig, and feed.text, so that the above case can be identified by determining if feed.title_orig == feed.text.

I've just found list parser and feel free to ignore this feature request!

But I hoped to use it to parse OPML and get the htmlUrl URLs from each item. But I think I'm right in saying that if an item has xmlUrl that will always be returned in feeds, and any htmlUrl ignored entirely?

Hi there.

The release history of listparser has been radio-silent for 7 years.

I am the author of https://github.com/Rongronggg9/RSS-to-Telegram-Bot. My project, published to PyPI using the package name rsstt, depends on listparser. I really love the current unreleased version and would like to upgrade to it. However, packages published to PyPI are not allowed to depend on packages outside PyPI. And I would neither like to publish my own listparser package nor like to bundle it inside my package, unless I have to.

That might be a somewhat rude question, but could I ask that is there a timetable for a new release?

lxml has bumped its major version due to an upstream (libxml2) breaking change.

https://github.com/lxml/lxml/blob/1a4362be12c99ec22f9859f3fe6455952256539f/CHANGES.txt#L60-L64

The link to https://listparser.readthedocs.io/en/stable/ results in a 404.