Re: [Python-Dev] Division of tool labour in porting Python 2 code to 2/3

2014-06-07 Thread Brett Cannon
On Sat Jun 07 2014 at 9:11:54 AM, Claudiu Popa wrote: > On Fri, Jun 6, 2014 at 7:37 PM, Brett Cannon wrote: > > After Glyph and Alex's email about their asks for assisting in writing > > Python 2/3 code, it got me thinking about where in the toolchain various > > warnings and such should go in o

Re: [Python-Dev] Division of tool labour in porting Python 2 code to 2/3

2014-06-07 Thread Claudiu Popa
On Fri, Jun 6, 2014 at 7:37 PM, Brett Cannon wrote: > After Glyph and Alex's email about their asks for assisting in writing > Python 2/3 code, it got me thinking about where in the toolchain various > warnings and such should go in order to help direct energy to help develop > whatever future too

Re: [Python-Dev] Division of tool labour in porting Python 2 code to 2/3

2014-06-06 Thread Brett Cannon
On Fri Jun 06 2014 at 2:29:13 PM, Terry Reedy wrote: > On 6/6/2014 12:37 PM, Brett Cannon wrote: > > After Glyph and Alex's email about their asks for assisting in writing > > Python 2/3 code, it got me thinking about where in the toolchain various > > warnings and such should go in order to help

Re: [Python-Dev] Division of tool labour in porting Python 2 code to 2/3

2014-06-06 Thread Terry Reedy
On 6/6/2014 12:37 PM, Brett Cannon wrote: After Glyph and Alex's email about their asks for assisting in writing Python 2/3 code, it got me thinking about where in the toolchain various warnings and such should go in order to help direct energy to help develop whatever future toolchain to assist