On 3/20/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: [snip] > Or we could just have 2.6 warn about the presence (or use) of __cmp__ > -- users can write equivalent code using __lt__ etc. themselves and > probably do a better job.
Fair enough. Is anyone collecting a list of these --py3k warnings? There seem to be a lot recent changes that 2.6's py3k-compat mode will be handling, but I haven't seen anything about someone tracking them/working on a PEP on the issue. Or did I just volunteer myself for that? : ) Collin Winter _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
