On Fri, May 29, 2009 at 13:33, Michael Foord <fuzzy...@voidspace.org.uk>wrote:
> Dino Viehland wrote: > >> Unfortunately there's probably going to continue to be a bunch of corner >> cases related to bytes/str/unicode until we move to 3.0. But hopefully >> we can come up w/ reasonable workarounds for most of them. >> >> In this case it seems like we should define __str__ on bytes and make >> it return a Unicode string w/o the b''. We can keep repr in there so >> that an explicit repr still gives you the b'' representation... >> >> Ahh, I can't wait until Ipy 3.0! >> >> > > In Python 2.6 the bytes type is just an alias for str I believe, am I > incorrect? If I am correct why is IronPython 2.6 taking a different > approach? > > Michael Correct. Include\bytesobject.h in CPython 2.6 source is just #defines to make the PyBytes* names available and pointing to PyString* names.
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
