On 2021/06/20 12:19, Daniel Jakots wrote: > On Sun, 20 Jun 2021 16:13:56 +0100, Kaashif Hymabaccus > <[email protected]> wrote: > > > Hello ports@, > > > > I was looking at upgrading mail/rss2email to 3.13.1, but this would > > require textproc/py-feedparser to be upgraded to version 6, due to > > rss2email relying on some changes made in version 6. > > > > The problem is that feedparser 6 makes several breaking changes, > > including completely dropping Python 2 support. > > > > Dropping Python 2 support is probably not a big deal for most ports > > (except perhaps www/canto, which I notice has "MODPY_VERSION = > > ${MODPY_DEFAULT_VERSION_2}"). > > https://github.com/themoken/canto-next seems to support python3, so > maybe updating it is enough?
design changed a bit, it is split into daemon and cli frontend, so probably wants treating basically as a new port. but yes. > > If a package drops support for Python 2 and another package needs it, > > how do we deal with that? Just remove the old package? Port the > > package to Python 3 and send patches to the authors? That last one > > seems not so trivial. > > You could also create a new port textproc/py2-feedparser with the last > version supporting legacy python. prefer to avoid this unless it's relatively important software and there's no good alternative to doing so (for example: numpy, Pillow, setuptools are used by a bunch of other ports including some which do still require py2 in the short term). in the case of canto: it's one dependent port, that hasn't seen a version update in the ports tree since it was first imported in 2010. (it split into the "canto-next" pieces in 2012 ish). I wouldn't have an objection to dropping it for now. (does it even still work?)
