Curt,
Thanks for the great explanation.
Max
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
We have an active bug against our new bytes implementation for 2.6. Currently
if you do:
b'***'[0]
you get back 42 as an int. This matches the 3.0 behavior of bytes but in
CPython 2.6 you get back '*'.
We could choose to match either form and then we could change it for 3.0. But
because
Keep it to 3.0 behavior because it answers the question of life, universe
and everything.
On Tue, May 5, 2009 at 11:26 PM, Dino Viehland di...@microsoft.com wrote:
We have an active bug against our new bytes implementation for 2.6.
Currently if you do:
b'***'[0]
you get back 42 as an
Dino Viehland wrote:
We have an active bug against our new bytes implementation for 2.6.
Currently if you do:
b'***'[0]
you get back 42 as an int. This matches the 3.0 behavior of bytes but
in CPython 2.6 you get back ‘*’.
We could choose to match either form and then we could change it
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
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
b'f\x00o\x00\x00' which I suspect will work for your purposes (but won't be
compatible
I guess the good news here then is that our post-2.6 planning is still
very unclear. While I'd love us to move to 3.0 to get rid of our
Unicode issues it seems like there's not enough movement forward in the
community at large - of course until then we're always going to have
subtle Unicode
Any updated timeline on this (IronPython 2.6/ASP.Net Integration)? Just
wanted to check in and see where it was on the list.
Thanks,
Adam
2009/3/30 Jimmy Schementi jimmy.scheme...@microsoft.com
A IronPython 2.6 version of the ASP.NET integration will be out shortly,
I have to get time to make
Rather than just releasing builds, I'm waiting on the OK from the ASP.NET to
release to source code for it, so it can be included in the IronPython releases
and the Codeplex sources/daily builds. That seems like a much better solution.
=) I'll keep you posted (I've been in conference-mode for
That is great news, and a great solution! Thanks!
Adam
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Jimmy Schementi
Sent: Tuesday, May 05, 2009 9:25 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Announcing IronPython 2.6
10 matches
Mail list logo
