IronPython 1.0 (1.0) on .NET 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.
>>> import base64
>>> base64.decodestring('w/==')
u'\xff'
Python 2.4.4 (#2, Oct 20 2006, 00:23:25)
[GCC 4.1.2 20061015 (prerelease) (Debian 4.1.1-16.1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import base64
>>> base64.decodestring('w/==')
'\xc3'
Now, imagine, what kind of debugging hell the above bug entailed.
I don't want to sound too harsh, but some parts of me are crying out
loud, "Python implementation with broken re, socket, and base64? And
they call it 1.0? What the hell? Are they serious?"
No Python programmers expect to debug re, socket, or base64 problems.
They are expected to just work. I can only agree with following quotes
of Baus:
"I'd rather just have a re module that worked :( I'm concerned that
there are still a ton of incompatabilities. This feels more like a
beta than a 1.x release."
Sorry.
--
Seo Sanghyeon
_______________________________________________
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
