Re: [Pythonmac-SIG] str.decode() behaves differently in 2.5 and 2.6

It seems as if 2.5 uses native byte order by default, and 2.6 big endian (if there's no Byte Orde Mark). Maybe a bug, maybe a bug fix, I don't know :). In the meantime, just use 'utf-16be' or 'uft-16le' explicitly or make sure there's a BOM. Just On Oct 12, 2008, at 12:42 PM, has wrote:

Re: [Pythonmac-SIG] str.decode() behaves differently in 2.5 and 2.6

Am 2008-10-12 um 12:42 schrieb has: Figure I should check here before filing a bug. Anyone understand the following discrepancy between 2.5 and 2.6: $ python2.5 Python 2.5.1 (r251:54863, Jan 17 2008, 19:35:17) [GCC 4.0.1 (Apple Inc. build 5465)] on darwin Type "help", "copyright", "credits" o

[Pythonmac-SIG] str.decode() behaves differently in 2.5 and 2.6

Hi folks, Figure I should check here before filing a bug. Anyone understand the following discrepancy between 2.5 and 2.6: $ python2.5 Python 2.5.1 (r251:54863, Jan 17 2008, 19:35:17) [GCC 4.0.1 (Apple Inc. build 5465)] on darwin Type "help", "copyright", "credits" or "license" for more infor