On 1/7/07, Anthony Baxter <[EMAIL PROTECTED]> wrote: > I've been thinking a little about how and where we'd add warnings to > 2.6 and later for things that will break in 3.0. My first idea is > to add a command line option '-3' (or maybe '-warn3') implemented > as "from __future__ import py3k". We can then put code in that > optionally generates a warning if this is set. > > I'm concerned that we don't make this check too expensive, though -
I have re-implemented warnings in C which should speed things up a bit (including start up). I need to polish it off and up load it. n _______________________________________________ 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
