On Thu, 16 Feb 2006 16:29:40 +0100, "M.-A. Lemburg" <[EMAIL PROTECTED]> wrote:
>Jean-Paul Calderone wrote:
>> On Thu, 16 Feb 2006 11:24:35 +0100, "M.-A. Lemburg" <[EMAIL PROTECTED]>
>> wrote:
>>> Neil Schemenauer wrote:
On Thu, Feb 16, 2006 at 02:43:02AM +0100, Thomas Wouters wrote:
> On
Jean-Paul Calderone wrote:
> On Thu, 16 Feb 2006 11:24:35 +0100, "M.-A. Lemburg" <[EMAIL PROTECTED]> wrote:
>> Neil Schemenauer wrote:
>>> On Thu, Feb 16, 2006 at 02:43:02AM +0100, Thomas Wouters wrote:
On Wed, Feb 15, 2006 at 05:23:56PM -0800, Guido van Rossum wrote:
>> from __fu
Giovanni Bajo wrote:
> Thomas Wouters <[EMAIL PROTECTED]> wrote:
>
from __future__ import unicode_strings
>>> Didn't we have a command-line option to do this? I believe it was
>>> removed because nobody could see the point. (Or am I hallucinating?
>>> After several days of non-stop discus
On Thu, 16 Feb 2006 11:24:35 +0100, "M.-A. Lemburg" <[EMAIL PROTECTED]> wrote:
>Neil Schemenauer wrote:
>> On Thu, Feb 16, 2006 at 02:43:02AM +0100, Thomas Wouters wrote:
>>> On Wed, Feb 15, 2006 at 05:23:56PM -0800, Guido van Rossum wrote:
>>>
> from __future__ import unicode_strings
Neil Schemenauer wrote:
> On Thu, Feb 16, 2006 at 02:43:02AM +0100, Thomas Wouters wrote:
>> On Wed, Feb 15, 2006 at 05:23:56PM -0800, Guido van Rossum wrote:
>>
from __future__ import unicode_strings
>>> Didn't we have a command-line option to do this? I believe it was
>>> removed because
Thomas Wouters <[EMAIL PROTECTED]> wrote:
>>> from __future__ import unicode_strings
>
>> Didn't we have a command-line option to do this? I believe it was
>> removed because nobody could see the point. (Or am I hallucinating?
>> After several days of non-stop discussing bytes that must be
>>
On Thu, Feb 16, 2006 at 02:43:02AM +0100, Thomas Wouters wrote:
> On Wed, Feb 15, 2006 at 05:23:56PM -0800, Guido van Rossum wrote:
>
> > > from __future__ import unicode_strings
>
> > Didn't we have a command-line option to do this? I believe it was
> > removed because nobody could see the p
On Wed, Feb 15, 2006 at 05:23:56PM -0800, Guido van Rossum wrote:
> > from __future__ import unicode_strings
> Didn't we have a command-line option to do this? I believe it was
> removed because nobody could see the point. (Or am I hallucinating?
> After several days of non-stop discussing by
On 2/15/06, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
> I'm in the process of summarizing the dicussion on the bytes object
> and an idea just occured to me. Imagine that I want to write code
> that deals with strings and I want to be maximally compatible with
> P3k. It would be nice if I could
On Thu, 16 Feb 2006 00:36:35 + (UTC), Neil Schemenauer <[EMAIL PROTECTED]>
wrote:
>I'm in the process of summarizing the dicussion on the bytes object
>and an idea just occured to me. Imagine that I want to write code
>that deals with strings and I want to be maximally compatible with
>P3k.
10 matches
Mail list logo