Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Jason Orendorff
On 2/22/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > If someone would like to volunteer a small PEP on the b"..." literal I > would appreciate it. I'll do this, unless someone tells me not to. A few questions. The grammar for string literals is already changing in py3k (removing the toleran

Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Blake Winton
Jason Orendorff wrote: > On 2/22/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: >> If someone would like to volunteer a small PEP on the b"..." literal I >> would appreciate it. > How do you feel about raw byte-strings (br'a\b\c') Not that my opinion particularly matters, but I would say "sure" t

Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Georg Brandl
Blake Winton schrieb: > Jason Orendorff wrote: >> On 2/22/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: >>> If someone would like to volunteer a small PEP on the b"..." literal I >>> would appreciate it. >> How do you feel about raw byte-strings (br'a\b\c') > > Not that my opinion particularly m

Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Thomas Wouters
I'm not telling you not to do this, but I already wrote a preliminary patch (well, it's not actually *working* yet, but the hard part, the grammar changes, are working ;) Of course, it may be fun to compare implementations. On 2/23/07, Jason Orendorff <[EMAIL PROTECTED]> wrote: On 2/22/07, Guid

Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Brett Cannon
On 2/23/07, Jason Orendorff <[EMAIL PROTECTED]> wrote: > On 2/22/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > If someone would like to volunteer a small PEP on the b"..." literal I > > would appreciate it. > > I'll do this, unless someone tells me not to. A few questions. > Thomas Wouters

Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Thomas Wouters
On 2/21/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: Patch anyone? See attachement. It's preliminary -- it just calls the global name 'bytes' currently (and not even using the 'right' AST concretion mechanism) which means you can override what the bytes literal creates by assigning to 'byt

Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Jason Orendorff
On 2/23/07, Thomas Wouters <[EMAIL PROTECTED]> wrote: > On 2/21/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > Patch anyone? > > See attachement. It's preliminary -- it just calls the global name 'bytes' > currently (and not even using the 'right' AST concretion mechanism) which > means you ca

Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Georg Brandl
Jason Orendorff schrieb: > On 2/23/07, Thomas Wouters <[EMAIL PROTECTED]> wrote: >> On 2/21/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: >> > Patch anyone? >> >> See attachement. It's preliminary -- it just calls the global name 'bytes' >> currently (and not even using the 'right' AST concretion

Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Greg Ewing
Blake Winton wrote: > What would: > b"""abc > def""" > translate into, exactly? > [ 97, 98, 99, 10, 100, 101, 102 ]? > [ 97, 98, 99, 13, 10, 100, 101, 102 ]? > Platform-dependent? (E!) No, presumably it would always translate the newline into "\n" regardless of platform, as with current stri

Re: [Python-3000] Thoughts on new I/O library and bytecode

2007-02-23 Thread Thomas Wouters
That's exactly what it does in current p3yk: Python 3.0x (p3yk:53867M, Feb 23 2007, 20:06:03) [GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)] on linux2 Type "help", "copyright", "credits" or "license" for more information. b"""abc ... def""" bytes([0x61, 0x62, 0x63, 0x0a, 0x64, 0x65, 0x66])