Curt Hagenlocher wrote:
On Mon, Mar 9, 2009 at 5:28 AM, Michael Foord <fuzzy...@voidspace.org.uk> wrote:
Curt Hagenlocher wrote:
I believe this is already fixed in the current (ie 2.6ish) source.
Any chance for 2.0.2?
That's Dino's call. The fix in 2.6 is actually a massive
restructuring of some code, so the backport would likely have to be
done from scratch against the 2.0 branch.
Fun fact: it wasn't fixed intentionally, and I only discovered the
problem in 2.0 by noticing that some (buggy) code was now broken with
2.6... :)
:-)
We're trying to see if we can get a performance benefit from using
__slots__ and the odd behaviour of 2.0.1. is, well, odd.
Michael
--
Curt Hagenlocher
c...@hagenlocher.org
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
