feedparser
feedparser copied to clipboard
kurtmckee
Debian 10 & 11: PEP479 Problem still exists
This issue is related to the current Debian 10 (stable) version of feedparser.
The PEP 479 problem is not fixed in there.
It was reported here https://github.com/kurtmckee/feedparser/issues/130
and fixed in upstream repository and prepared for release in version 6.0.0 https://github.com/kurtmckee/feedparser/pull/131
I asked on the Debian python mailinglist to ask what need to be done to bring the debian package back to life. https://alioth-lists.debian.net/pipermail/python-modules-team/2019-December/061104.html
Waiting for feedback and will report here.
No answer on the debian mailinglist. I opened an official debian bug report.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946788
Hi Kurt, I had some discussions on Debians IRC channel.
They strongly recommand to do a minor release of feedparser only fixing this bug - not more. Then there is chance to get this version into current stable.
Sideinformation: I inserted (via vim as root) the bugfixing lines into my feedparser installation (debian package 5.2.1-1). It is fixed then and the problem is not reproducable anymore.
Thanks for taking point on this! I'll release a hotfix 5.2.2 to handle this issue for Debian.
On December 15, 2019 3:37:18 PM CST, Codeberg-AsGithubAlternative-buhtz [email protected] wrote:
No answer on the debian mailinglist. I opened an official debian bug report.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946788
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kurtmckee/feedparser/issues/198#issuecomment-565849379
Super, I'll branch off tag 5.2.1 and add the fix.
On December 15, 2019 10:49:09 PM CST, Codeberg-AsGithubAlternative-buhtz [email protected] wrote:
Hi Kurt, I had some discussions on Debians IRC channel.
They strongly recommand to do a minor release of feedparser only fixing this bug - not more. Then there is chance to get this version into current stable.
Sideinformation: I inserted (via vim as root) the bugfixing lines into my feedparser installation (debian package 5.2.1-1). It is fixed then and the problem is not reproducable anymore.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kurtmckee/feedparser/issues/198#issuecomment-565903555
Dear Kurt, I see your worked a lot in the last days. Great!
The Debain community would be happy if you would release the 5.2.2 version so the Debian package can be fixed.
Haven't forgotten, but I'm glad you pinged this ticket again! There was recently a second StopIteration PR for georss.py from...I think ChanceDuress? Would you double-check to see if that's necessary for inclusion as well?
On February 25, 2020 8:36:36 AM UTC, Codeberg-AsGithubAlternative-buhtz [email protected] wrote:
Dear Kurt, I see your worked a lot in the last days. Great!
The Debain community would be happy if you would release the 5.2.2 version so the Debian package can be fixed.
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kurtmckee/feedparser/issues/198#issuecomment-590747880
Sorry about the confusion. #181 looks like it might be related so I wanted to confirm whether that's helpful to include as well?
On February 25, 2020 2:21:35 PM UTC, Codeberg-AsGithubAlternative-buhtz [email protected] wrote:
Sorry, but I do not understand.
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/kurtmckee/feedparser/issues/198#issuecomment-590890004
