[Python-3000] Moving forward: library reorganization (original) (raw)
Thomas Wouters thomas at python.org
Tue Dec 19 02:11:03 CET 2006
- Previous message: [Python-3000] Py3k release schedule worries
- Next message: [Python-3000] Moving forward: library reorganization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/18/06, Guido van Rossum <guido at python.org> wrote:
Ok, so be it. Let this be a pronouncement -- the only stdlib reorg we're doing will be (a) deleting silly old stuff; (b) rename modules that don't conform to the current module/package naming convention, like StringIO, cPickle or UserDict.
Let's discuss some practicalities then. How about we just start renaming modules in the p3yk branch, and make a new lib-old (it's currently empt) that holds aliases for the old names -- but that raise an ImportWarning when imported. (If that warning class still exists -- something tells me we disabled again, but I don't remember the details.) The refactoring tool should be usable for code rewrites, I think, considering there won't be any implicit relative imports anymore, but we could do it by search-and-replace or spot-the-warnings, too.
-- Thomas Wouters <thomas at python.org>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-3000/attachments/20061218/ee2458fd/attachment.html
- Previous message: [Python-3000] Py3k release schedule worries
- Next message: [Python-3000] Moving forward: library reorganization
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]