Hi team, How should we handle a port update which breaks the (EOL) python2 FLAVOR?
I had the issue on net/py-urwid which I didn't initially catch. But their latest version uses async stuff that aren't supported in py2 nor will be. So I am wondering what would be the best way to proceed. 1/ Should we wait for py3 to become default to update these ports? And they become py3 only? will py2 still be a legacy FLAVOR? how to handle the RUN_DEPENDS? 2/ Should we have two versions of the port? The latest being py3 only? What would be the prefered way to enforce this? Then progressively update RUN_DEPENDS switching them to py3 as well. 3/ ... any other way ? Open for comments. I am sure some of you already have kind of a plan to make the switch at some point. Thanks. -- clematis (0x7e96fd2400fe7b59)
