On 3/21/07, Collin Winter <[EMAIL PROTECTED]> wrote: > 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? : )
PEP 361 lists some, although I'm sure it could use some love and care. I would especially appreciate clarity on what the warning flags are, what warnings are active under each flag, etc. Anthony Baxter has patches for two of the warnings: http://sourceforge.net/tracker/index.php?func=detail&aid=1631035&group_id=5470&atid=305470 I have a patch for several more: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1683908&group_id=5470 -- Adam Olsen, aka Rhamphoryncus _______________________________________________ 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
