[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Python 2 d-d-a proposal



On Wed, Apr 15, 2015 at 3:27 PM, Paul Tagliamonte <paultag@debian.org> 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.


Thanks!
  Paul

--
 .''`.  Paul Tagliamonte <paultag@debian.org>  |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `-     http://people.debian.org/~paultag/conduct-statement.txt


Hey everyone!

I realize I haven't made a formal introduction of myself to this list (I'll do that some other time), but I have a fairly significant amount of experience adding Python 3 compatibility to tools while retaining Python 2 compatibility (I recently just helped SQLObject release 3.0.0a1 which is the first version to support Python 3.4). We might want to move to making the tools compatible first and then drop support for Python 3. Also, I'm very much up for helping with this.

Cheers,
Ian

Reply to: