> Given the naming that Python eventually settled on, it might be worth > renaming RawStr() to Bytes() to cut down on confusion.
Agreed, we should implement support for Bytes, except I think we shouldn't rename RawStr to it, but rather use Bytes exclusively to represent the new "bytes" type, offering people the chance of a smooth migration (Python 2.6 has both strings and bytes). Out of curiosity, the name of RawStr is also like that to avoid confusion with the upcoming naming conventions. "str" in Python 3.0 is actually unicode, so it'll be natural to have Str in Storm some day to represent it. -- Gustavo Niemeyer http://niemeyer.net -- storm mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/storm
