> > No; basically, you just need to be patient now. Do you have an urgent > need to get this patch included? Well, not personally, but I suspect that it is quite possible that other people will waste time trying to figure out why their imports don't work. Also, seeing that there are almost 400 open patches in the patch tracker, I'm concerned that this patch will be forgotten and left to rot, which would be a pity IMO. One issue is whether this patch should be backported to the 2.5 branch; > as it is arguably a new feature, it probably should not. As 2.6 is still > quite some time ahead, I can't see any urgency. I see this more as a fix rather than a new feature, as there is no reason or explanation in the documentation (that I've been able to find) to suggest that importing built-in submodules shouldn't work. The small changes to the code in the patch also "feel" more like a fix than like a new feature. So yes, ideally I would like to see this patch in 2.5.1, although I will of course defer to the people who are in charge of making that decision. Regards, Miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20070312/1b212871/attachment.html
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4