On Jan 1, 2008 11:32 AM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > I don't like renaming PyString to PyBytes right now -- in 2.6 this
> > sounds wrong since it is publicly known as the str[ing] type. Renaming
> > only in 3.0 would make merges from the trunk harder. (
On Jan 1, 2008 12:15 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I thought PEP 3016 spells out all the details necessary. And the
> docstring for open() in io.py as well. Aren't those enough?
>
Oh, indeed. I didn't remark that PEP 3116 had a section about newline
conversion. It's my mistake
Guido van Rossum wrote:
> I don't like renaming PyString to PyBytes right now -- in 2.6 this
> sounds wrong since it is publicly known as the str[ing] type. Renaming
> only in 3.0 would make merges from the trunk harder. (Unless you have
> evidence to the contrary?)
>
> I'm okay with renaming PyBy
I don't like renaming PyString to PyBytes right now -- in 2.6 this
sounds wrong since it is publicly known as the str[ing] type. Renaming
only in 3.0 would make merges from the trunk harder. (Unless you have
evidence to the contrary?)
I'm okay with renaming PyBytes -> PyByteArray, PyBuffer ->
PyMe
I thought PEP 3016 spells out all the details necessary. And the
docstring for open() in io.py as well. Aren't those enough?
On Dec 27, 2007 11:19 PM, Alexandre Vassalotti <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I had a hard time, earlier today, figuring out what was the rules for
> converting newlin
