I'll add a note about that, and talk with the ftpteam to see if we can implement that policy in NEW.
Mails on the thread seem positive so far, I'll post this to d-d-a when I get home from YUL to DC tonight. On Apr 15, 2015 5:07 PM, "Matthias Klose" <d...@debian.org> wrote: > On 04/15/2015 10:27 PM, Paul Tagliamonte wrote: > > Heyya d-p, > > > > I'd like to send an email to d-d-a asking that project to consider no > > longer creating new Debian tools in Python 2. > > > > I'd like this to have the endorsement of the team, so, does anyone > object to > > me asking people to not write new tools in Python 2 only (prefer > alternative > > deps or porting), and only use Python 2 in very special curcumstances or > > for legacy codebases (perhaps a pitch to move to Python 3), along with a > > note that we plan to deprecate Python 2 when upstream support is gone > > (2020), which puts us on track for two cycles (Buster) > > > > > > I'll make note of a team which should exist to help with such porting, > > (I'm up to help with this) that was one of the items that came out of > > the PyCon chit-chat. I got the sense from the room that this would be > > OK, but just checking if anyone here has a substantive objection. > > > > If not, I'll send that out later on today/tomorow. > > sure, please could you also propose not to accept new packages which are > Python3 > compatible upstream, but use Python2 in the packaging? Same thing for > modules > when Python3 is supported upstream, but only the Python2 module is > packaged. > > Matthias > > > -- > To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: https://lists.debian.org/552ed301.9030...@debian.org > >
