On Mon, Feb 1, 2010 at 2:46 PM, Dino Viehland <di...@microsoft.com> wrote: > Messing with identity starts to get really scary and I'd rather not go > there - I'm sure there will be lots of edge cases which will be broken. > > I could see is making unicode(foo) do something different. If you aliased > unicode then you'd get str's behavior though but that might be perfectly > acceptable. It's definitely a solution I had not considered and it'd > probably fix multiple issues.
Hi Dino, It looks like this is a major impediment to running Django; the majority of the test suite failures are because IronPython calls __str__ instead of __unicode__. Any chance this could be fixed for 2.6.1? I know it's a big change, but IMHO it's pretty critical as well. - Jeff _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com