feed2exec (0.17.1) [PTS] [DDPO]

COMMITS: VCS has seen 2 commits since the 0.17.1 tag

Git: https://gitlab.com/anarcat/feed2exec
Enter a full Vcs-* header, supported schemes are: Vcs-Bzr, Vcs-Cvs, Vcs-Darcs, Vcs-Git, Vcs-Hg, Vcs-Mtn, Vcs-Svn.
For Vcs-Git append -b branch to select the branch name; append [subdir] if the debian/ directory is not in the repository root.
The next upload will reset the information from the source package headers.
Branch: master
Path: debian/changelog
Browser: https://gitlab.com/anarcat/feed2exec/tree/master
Last scan: 2021-03-06 20:02:02+00
Next scan: 2021-03-07 16:38:00+00

Debian changelog in Git:

feed2exec (0.17.1) unstable; urgency=medium

  * fix unit tests in a clean environment

 -- Antoine Beaupré <anarcat@debian.org>  Thu, 04 Feb 2021 17:14:59 -0500

This branch is 2 commits ahead of tag 0.17.1

Git log:

commit c7b6f73686178725eb348c67d0cf0b58fa308f65
Author: Antoine Beaupré <anarcat@debian.org>
Date:   Thu Feb 25 09:50:08 2021 -0500

    fix crash in feed2exec parse
    
    For some reason, I was getting this backtrace here when running a test
    feed:
    
        plugin generated exception: expected str, bytes or os.PathLike object, not NoneType, skipping
        Traceback (most recent call last):
          File "/home/anarcat/src/feed2exec/feed2exec/plugins/__init__.py", line 105, in output
            return plugin.output(*args, feed=feed, item=item, lock=lock)
          File "/home/anarcat/src/feed2exec/feed2exec/plugins/maildir.py", line 42, in __init__
            prefix = os.path.expanduser(feed.get('mailbox', '~/Maildir'))
          File "/usr/lib/python3.7/posixpath.py", line 235, in expanduser
            path = os.fspath(path)
        TypeError: expected str, bytes or os.PathLike object, not NoneType
    
    This was caused by the maildir plugin constructor, which was looking
    up the `mailbox` field in the field. Because that is unset in my
    feed2exec.ini (because I was testing against a new feed), that
    `mailbox` key was just not present. The feedparser dict behavior in
    this case is to return None, instead of the default, which I find
    strange and unusual.
    
    Tests still seem to pass here after the patch, so I guess this should
    work in the future, and does un-break the feed test.
    
    I can't quite figure out how to come up with a unit test for that one,
    but now I can't help but think that feed configuration should just be
    split up from the feedparser dict, because so much of those issues
    come from that (strange) coupling.

commit a44497c1ef055d6891accfad47c549a6f6d31ac1
Author: Antoine Beaupré <anarcat@debian.org>
Date:   Mon Feb 8 15:49:17 2021 -0500

    mention (lack of) Gemini and other protocol support