[Python-Dev] Py3k DeprecationWarning in stdlib (original) (raw)

Guido van Rossum guido at python.org
Tue Jun 24 18:42:29 CEST 2008

The same generic warning against sweeping changes applies here though. You have to manually review each change. The stdlib and especially the test suite is likely to break if you just let 2to3 run over it, even just a single fixer like fix_has_key.

On Tue, Jun 24, 2008 at 6:11 AM, Benjamin Peterson <musiccomposition at gmail.com> wrote:

On Tue, Jun 24, 2008 at 8:08 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:

Benjamin Peterson wrote:

On Tue, Jun 24, 2008 at 5:34 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:

I'd say so, yes. If tracker issues don't exist yet, please create them. The focus for the first beta was really on getting all the syntax and API changes stable - the remaining time between the first beta release and the first release candidate will focus on cleaning up issues like this. I wonder if we could just 2to3 (with fixers that create incompatibilities disabled) over the whole stdlib and see what happens. Just running the unit test suite with -3 would probably be a better starting point. 2to3 makes a lot of extra changes that we don't particularly care about. Right, which is why I suggest running a few fixers (ie fixhaskey) and then tearing the test suite apart. -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1."

Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org

-- --Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-Dev mailing list