Control: reassign -1 python3-feedparser On 2020-07-09 12:51:37, WhilelM wrote: > Package: feed2exec > Version: 0.15.0 > Severity: important > > Hello, > > Would you mind take a look into it? > > Thank you so much. > > > --Systen DB: {'url': 'http://www.agendadulibre.org/events.rss?region=12', > 'output': 'feed2exec.plugins.maildir', 'folder': > '/home/whilelm/maildir/feed2exec/', 'name': > 'http___www.agendadulibre.org_events.rss_region_12'} > fetching feed http://www.agendadulibre.org/events.rss?region=12 > Starting new HTTP connection (1): www.agendadulibre.org:80 > http://www.agendadulibre.org:80 "GET /events.rss?region=12 HTTP/1.1" 302 161 > Starting new HTTPS connection (1): www.agendadulibre.org:443 > https://www.agendadulibre.org:443 "GET /events.rss?region=12 HTTP/1.1" 200 > 4990 > parsing feed http://www.agendadulibre.org/events.rss?region=12 (68668 bytes) > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/feedparser.py", line 3774, in > _gen_georss_coords > t = [nxt(), nxt()][::swap and -1 or 1] > StopIteration
Hi! It looks like this is actually a problem with feedparser, who can't recover after some problem while parsing the feed. So I think the problem is rather more with feedparser than with feed2exec, although maybe we could handle that problem better inside feedparser... Plain feedparser reproducer: python3 -c 'import feedparser; feedparser.parse("http://www.agendadulibre.org/events.rss?region=12")' Could you report it upstream (or look if present already): https://github.com/kurtmckee/feedparser/issues Thanks for the bug report! a. -- Le travail des pauvres est la seule source de toutes les douceurs de l'existence. - Bernard Mandeville