Matt Giuca <[EMAIL PROTECTED]> added the comment: I renamed tostring/fromstring to tobytes/frombytes in the array module, as described above. I then grepped the entire py3k tree for "tostring" and "fromstring", and carefully replaced all references which pertain to array objects.
The relatively minor number of these references suggests this won't be a big problem. All the test cases pass. I haven't (yet) renamed tounicode/fromunicode to tostring/fromstring. The more I think about it, the more that sounds like a bad idea (and could create confusion as to whether this is a character string or byte string, as Martin pointed out). The patch (doc+bytesmethods.patch) does both the original doc-only.patch, plus the renaming and updating of all usages. Use the above commit log, plus: Renamed array.tostring to array.tobytes, and array.fromstring to array.frombytes, to reflect the Python 3.0 terminology. Updated all references to these methods in Lib to the new names. Added file: http://bugs.python.org/file11122/doc+bytesmethods.patch _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3565> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
