> Please don't -- a Py3k warning makes no sense if the feature isn't really > going away in Py3k. Py3k warnings really should only warn about things > that are going to break in 3.0. > > If the decision is reached that such a warning makes sense, I'd propose > to only warn in an "extended Py3k warning mode" activated with -33. A Py3k warning is already a extended DeprecationWarning! Why don't we just give it a DeprecationWarning in 3.0? > > Georg
-- Cheers, Benjamin Peterson _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
