On 2019/02/18 02:00, Kurt Mosiejczuk wrote: > On Mon, Feb 18, 2019 at 12:49:29AM -0500, Kurt Mosiejczuk wrote: > > > py-typing backports the typing functionality from 3.6+ to python > > versions before 3.5. Since we ship 3.6.8 now, there is no longer a > > reason to have a python3 flavor. Installing a python3 version does > > nothing at this point. So I removed the python3 flavor. > > An interesting side effect of this is that ports that depend on it > need to be tweaked *not* to depend on it for a Python 3 version. I've > sent out a patch for the py-aiodns port I maintain. I have a patch > for py-dnspython also, but many more things depend on py-dnspython, > including mailman, samba, and more. > > That's a lot of dependencies to check to see if I am throwing a monkey > wrench into the works. Should I start testing all those ports and > flavors of samba? Realistically py-typing should do nothing for python3 > so these changes *should* be a no-op. Should I maybe redo the update of > py-typing without killing the python3 flavor? > > --Kurt >
my 2c: at this point in the release cycle, that's probably the safer way to go, leaving an explanatory comment next to the flavour bits. After we're done with 6.5 go through killing them (and for py-typing itself add a comment explaining why there's no py3 flavour otherwise I expect someone will try to re-add it later ;)
