[Piuparts-devel] [py3porters-devel] when to remove python2 support? (was Re: [Needs Port] piuparts.debian.org
Dimitri John Ledkov
xnox at debian.org
Tue Apr 28 13:45:10 UTC 2015
On 28 April 2015 at 13:29, Holger Levsen <holger at layer-acht.org> wrote:
> Hi Bernhard,
> On Montag, 27. April 2015, Bernhard Janetzki wrote:
>> i had to rewrite some import statements using the six lib:
>> - i’ll need some more six functionality for the upcoming refactoring
>> - if we need to remove py2 support in some years (haha), it’s much easier
>> to search for the six stuff and eliminate it
>> - cleaner syntax
>> commit c23f83e524f4c6ffa3f17f5f76d63902507b994c
> cool, cherry-picked, thanks!
> And re: "if we need to remove py2 support in some years (haha)" - I'm not sure
> why we shouldn't remove python2 support in a *few* *months*! As long as the
> new python3 codebase keeps working with python3 in wheezy, jessie and stretch.
> And I'm not even really sure how useful it is to keep it running in wheezy -
> opinions or advice anyone?
In general, we can start removing python2 support from leaf nodes
first... so a given thing is an app and doesn't have public modules
which other packages use, you can go ahead and drop python2 support.
Similarly for library packages once there are no longer any python2
reverse dependencies, python2 package can be dropped as well. And so
Quite a few apps are python3 "only" already.
More information about the Piuparts-devel