On Tue, May 5, 2009 at 6:10 PM, Dino Viehland di...@microsoft.com wrote:
Ok, I do have a fix for this and the other issues - I'm just waiting for
a code review then I'll check it in. If we do f.write(buffer('foo')) where
f was opened as a binary file we'll write out b'foo' and not
On Mon, May 4, 2009 at 2:13 PM, Dino Viehland di...@microsoft.com wrote:
You mention bug #22258 - is Mercurial using byte array notation wherever
they intend to have a non-Unicode string?
Turns out, I thought buffers == byte arrays, but apparently they're
not. I also managed to mix up changes
Sent: Tuesday, May 05, 2009 4:58 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Mercurial Status
On Mon, May 4, 2009 at 2:13 PM, Dino Viehland di...@microsoft.com
wrote:
You mention bug #22258 - is Mercurial using byte array notation
wherever
they intend to have a non-Unicode
...@lists.ironpython.com] On Behalf Of Jeff Hardy
Sent: Saturday, May 02, 2009 12:24 PM
To: Discussion of IronPython
Subject: [IronPython] Mercurial Status
I've been testing IronPython with Mercurial. Using the 2.6 nightlies as
the base, lots of it will just work. (Make sure you grab zlib from
http
I've been testing IronPython with Mercurial. Using the 2.6 nightlies
as the base, lots of it will just work. (Make sure you grab zlib
from
http://cid-414fa1a9bd174b4b.skydrive.live.com/self.aspx/Public/IronPython.Zlib.zip).
The attached patch moves things a little further on. Also, you'll need
to
