Re: [PATCH] Replace print statement with sys.stdout.write for python3 compatibility

2013-12-05 Thread Colin Watson
On Thu, Dec 05, 2013 at 04:31:55PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > On 04.12.2013 16:28, Mike Gilbert wrote: > > On Wed, Dec 4, 2013 at 5:12 AM, Colin Watson wrote: > >> On Tue, Dec 03, 2013 at 08:14:09PM -0500, Mike Gilbert wrote: > >>> Gmail likes to mangle patches, so I'm

Re: [PATCH] Replace print statement with sys.stdout.write for python3 compatibility

2013-12-05 Thread Vladimir 'φ-coder/phcoder' Serbinenko
On 04.12.2013 16:28, Mike Gilbert wrote: > On Wed, Dec 4, 2013 at 5:12 AM, Colin Watson wrote: >> On Tue, Dec 03, 2013 at 08:14:09PM -0500, Mike Gilbert wrote: >>> Gmail likes to mangle patches, so I'm attaching it. >> >> Could we please use the clearer bilingual form of "from __future__ >> import

Re: [PATCH] Replace print statement with sys.stdout.write for python3 compatibility

2013-12-04 Thread Mike Gilbert
On Wed, Dec 4, 2013 at 5:12 AM, Colin Watson wrote: > On Tue, Dec 03, 2013 at 08:14:09PM -0500, Mike Gilbert wrote: >> Gmail likes to mangle patches, so I'm attaching it. > > Could we please use the clearer bilingual form of "from __future__ > import print_function" at the top followed by print(s,

Re: [PATCH] Replace print statement with sys.stdout.write for python3 compatibility

2013-12-04 Thread Colin Watson
On Tue, Dec 03, 2013 at 08:14:09PM -0500, Mike Gilbert wrote: > Gmail likes to mangle patches, so I'm attaching it. Could we please use the clearer bilingual form of "from __future__ import print_function" at the top followed by print(s, end="")? This does require bumping our minimum required Pyt