On Mon, May 19, 2008 at 5:10 PM, Raymond Hettinger
From: "Brett Cannon"
So, here is my idea (only need to care about modules that have stuff to pickle, e.g., don't need to change test.support):
* Rename lib-old to lib-new
* Change the names in lib-new to the new names.
* Change the names in the stdlib to the old names.
* Move the Py3K warnings out of the stubs in lib-new and put them in the modules directly stored in the stdlib.
* Change the imports in the stubs in lib-new to import the old name and suppress the Py3K warning (probably use test.support.catch_warning() with a *very* specific ignore filter).
That plan seems harmless enough, but why bother?
Same reason given on python-dev when you asked this question before. =) 2.6 is supposed to minimize the differences between 2.x and 3.0 as much as possible without having to run 2to3. Plus I don't want to have to change imports in patches between 2.6 and 3.0 if I don't have to. -Brett