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
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
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,
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
Gmail likes to mangle patches, so I'm attaching it.
From 1ac0d1f8feda7cbbe3e706074aebcc805e4f3667 Mon Sep 17 00:00:00 2001
From: Mike Gilbert
Date: Tue, 3 Dec 2013 20:06:07 -0500
Subject: [PATCH] Replace print statement with sys.stdout.write for python3
compatibility
---
ChangeLo
