<br><br><div><span class="gmail_quote">On 12/18/06, <b class="gmail_sendername">Thomas Wouters</b> <<a href="mailto:thomas@python.org">thomas@python.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><div><span class="gmail_quote">On 12/18/06, <b class="gmail_sendername">Guido van Rossum</b> <<a href="mailto:guido@python.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">guido@python.org
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Ok, so be it. Let this be a pronouncement -- the only stdlib reorg<br>we're doing will be (a) deleting silly old stuff; (b) rename modules<br>that don't conform to the current module/package naming convention,<br>like StringIO, cPickle or UserDict.
</blockquote><div><br>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.
</div></div></blockquote><div><br>ImportWarning is still there; it's used when you try to import a directory that doesn't have an __init_.py . It's tested in the test suite.<br><br>As for using a lib-old idea, is that for Python
2.x to help transition, or did you want to do that for Py3K as well? I see the logic in the former to help transition but in the latter.<br></div><br></div>-Brett<br>