API refactoring: create a Feed class
A "Feed" is the basic representation of a RSS/Atom feed. It derives from the feedparser dict but we use our class to regroup functionality that was loose around the module, like normalize() and...
View Articlesecurity: avoid possible config setting override
It may be possible for parsed feed data to override configuration that is passed to plugins and other components. Normally, feedparser doesn't send those settings (e.g. output or args) that could...
View Articlecosmetic: consistent test comparison
We should do "expected == actual" because that is the way the diff is ordered on display. That's a rather opiniated way of doing things, but at least we should be consistent across the board, which we...
View Articleadd transmission plugin
this plugin is introduced because the exec plugin cannot safely guess a subdirectory to save feed into without resorting to using plugins. now the transmission plugin has nicer defaults and properly...
View Articlemove fetch functionality to Feed
this allows to make for simpler tests, because we can easily fetch and parse a single object instead of having to run over a full config furthermore, it is more logical for plugins: they get passed a...
View Articlemove catchup down into plugins
output plugins are now actually called when catchup is used. responsability to skip slow and write operations are delegated to plugins, which makes them easier to develop and test
View Articlefollow redirections in wayback machine
requests that would hit logos on my blog were triggering 302 status which were considered failures. not sure where there's such a discrepancy between html pages and icons, but it makes sense to follow...
View Article
