Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: On 2008-12-09 00:58, Antoine Pitrou wrote: > Antoine Pitrou <[EMAIL PROTECTED]> added the comment: > > I wrote: >> IMO PyUnicode_Compare() should be replaced by a hypothetical >> PyObject_RichCompare(), which allows to take shortcuts when comparing >> strings of different length and a Py_EQ or Py_NE comparison is requested. > > ... and I didn't even remember that PyUnicode_RichCompare() already > exists. So let my proposal be to enable those optimizations inside the > existing PyUnicode_RichCompare(), and dump PyUnicode_Compare().
What for ? What does this have to do with removing __cmp__ ? Why do you want to break the C API for no apparent reason ? I've designed the Unicode C API to be a rich API and would like it to stay that way. _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1717> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
