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

Benjamin Peterson musiccomposition at gmail.com
Tue Jun 24 15:11:00 CEST 2008

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 fix_has_key) and then tearing the test suite apart.

-- Cheers, Benjamin Peterson "There's no place like 127.0.0.1."

More information about the Python-Dev mailing list