> Right, but in one version of Python "str" means raw bytes, and "bytes" > means raw bytes as well, and on another one "str" actually means > unicode, and "bytes" means something newly introduced which is > incompatible. This scheme feels like a pretty poor choice to me due > to the ambiguities. Types are named exactly the same way, but behave > very differently.
Here is a more careful analysis of why I think this is bad: http://blog.labix.org/2009/07/02/screwing-up-python-compatibility-unicode-str-bytes -- Gustavo Niemeyer http://niemeyer.net -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
