Thanks! (I actually didn't get back until today, and lots of e-mail & meetings so far today, so I just hadn't gotten the chance yet...)
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Patrick Dubroy Sent: Tuesday, November 27, 2007 11:29 AM To: Discussion of IronPython Subject: Re: [IronPython] Problems with 8-bit strings I didn't see a bug open, so I opened one: http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=14104 Thanks, Pat On Nov 24, 2007 3:54 PM, Dino Viehland <[EMAIL PROTECTED]> wrote: > I think the construction w/ characters > 0x80 is a bug. But the returning of > unicode vs. 8-bit strings is just a display issue. IronPython only has > unicode strings and is one of the big differences between CPython and > IronPython. If you haven't already I'll open a bug when I'm back after > Thanksgiving. > > ________________________________________ > From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Patrick Dubroy [EMAIL > PROTECTED] > Sent: Wednesday, November 21, 2007 12:18 PM > To: users@lists.ironpython.com > Subject: [IronPython] Problems with 8-bit strings > > > Hi, > > I've noticed that in the latest version of IronPython (2.0A6), I > noticed some weird behaviour with 8-bit strings: > > IronPython console: IronPython 2.0A6 (2.0.11102.00) on .NET 2.0.50727.1378 > Copyright (c) Microsoft Corporation. All rights reserved. > >>> str("\x7e") > '~' > >>> str("\x7f") > u'\x7f' > >>> str("\x80") > u'\x80' > >>> str("\x81") > Traceback (most recent call last): > File , line 0, in ##23 > File mscorlib, line unknown, in GetString > File mscorlib, line unknown, in GetChars > File mscorlib, line unknown, in Fallback > File mscorlib, line unknown, in Throw > UnicodeDecodeError: Unable to translate bytes [81] at index 0 from > specified code page to Unicode. > > The first problem is that if the string contains characters 127 (0x7F) > or 128 (0x80), str() will return a Unicode string rather than an 8-bit > string. CPython, on the other hand, returns a standard 8-bit string > for both of those cases. Then, if the string contains any bytes > greater than 128, it throws an exception. CPython, on the other hand, > is happy to have bytes up to 0xFF in an 8-bit string. > > Is this a known issue? Should I open a bug? > > Pat > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com