fix broken cache adapter support
We did not need to pass the if-modified-since header. All that was needd was that we lookup (and return!) the cache value properly. So also remove that from the database. The way things were setup,...
View Articleforcibly preset the builtin feed session
Without this setting, the wrong session gets initialized in the new Feed object. Before the caching layer was implemented, this didn't matter much because those sessions were never called. But since...
View Articleinstall python3-dev, required for compiling regex
Not sure why all that junk is necessary, but I want to fix the build.
View Articleavoid newer feedparser versions
feedparser 6.0+ removed the FeedParserDict which we depend on: https://github.com/kurtmckee/feedparser/issues/197 Until we refactor the Feed class, stick with older versions of feedparser.
View Articlemove session and fetching to the feed manager
Having the session and the network code in the "model" makes no sense: that stuff belongs in the "controller". Having it there made it particularly difficult to implement the caching layer, as I had...
View Articleremove class-level sticky session parameter
This cleans up a lot of stuff. Now we can treat the session as a normal feed_manager parameter. Since there is usually only one feed_manager in operation at any time, it is basically a static member....
View Articlemake test suite pass again
This was failing because hooking up the cache into the session completely obliterates our poor old betamax cache. Instead of doing that, we politely queue the cache layer behind it... ... except that...
View Articlerename feeds to feed_manager in main
The "feeds" appelation is an old remnant of the previous data structures. Now we do use a FeedManager everywhere and we should name it as such. It will be easier to grep for it and will more obviously...
View Articlereuse feed_manager object in fetch as well
I see no reason why we need to construct a different object in this specific class, let's just reuse the one already created. This should make a tiny improvement on the startup latency, but hasn't...
View ArticleDRY: refactor common requirements out of tox and setup.py
Requirements are now stored only in setup.py. Before, we were telling tox to delegate the test runs to setup.py, but this made it impossible to pass arguments to pytest. By calling pytest directly, we...
View Articleexplicitely override the feed, not the session
This gives us a single override point that is more cohesive and cleaner. It will also make other run tests much easier to call, but that's for a later commit.
View Articleremove useless --config and --database and override instead
By passing the feed_manager, we have complete and coherent control over those parameters, without having to pass along the arguments. The downside is we create empty cassettes for all of those, but...
View Articleadd empty test cassettes artifacts
Those seem to be created now that we use the betamax session everywhere, but they are probably harmless.
View ArticleREADME: don't let the example config create a folder named '~/Mailbox/'
I was confused that feeds didn't show up in my usualy location, but on further investigation, I found out that I now had a new subfolder in my home folder, literally named '~: $ find ./"'~"...
View ArticleMerge branch 'master' into 'master'
README: don't let the example config create a folder named '~/Mailbox/' See merge request anarcat/feed2exec!7
View Articlerecover from feedparser exceptions (Closes: #964597)
In the aforementionned bug report, feed2exec crashes brutally (with a backtrace, and not completely done) on the following feed: http://www.agendadulibre.org/events.rss?region=12 The full backtrace...
View Articlerun tox on whatever python environment is available
This removes a duplicate source of information about where to store Python versions. The classifiers remain, however. This makes the `tox` command (ran locally on my laptop) work without errors too.
View Articleadd known failing black environment
That .gitlabci came from undertime, so I think it's okay to keep it around. I'm just not ready to basically rewrite the entire source code here just yet however, so silence errors from black for now.
View ArticleFix --loglevel option spec
The --loglevel command line option is not a flag but a choice. Consequently, it needs a *default* and not a *flag_value*.
View ArticleOkay, try a --quiet option instead
As discussed in Issue #13, a way is needed to hide warnings but show errors. Since we apparently cannot have a general loglevel option, this commit provides a way to set that particular loglevel.
View ArticleArgh! Working around click is getting entirely unreasonable.
Looks like the loglevel is _still_ not set unless every option that _may_ set it has a default value. Or?
View ArticleAPI change: allow absolute path in folder setting
This resolves a bunch of issues, detailed in #14. But basically, I was assuming users would never specify an absolute path in `folder`. But it turns out this was natural for at least one user: they...
View Articlesilence pytest warning
the regression mark is some thing I found in another project but I never defined here. it's kind of useless anyways: just use a proper doc string instead.
View Article
