On Saturday 01 July 2006 12:55, Guido van Rossum wrote: > It's up to the release manager now to decide whether the pitchforks > at Google or the pitchforks in the larger Python community are > sharper. ;-) At this point, I think removing the warning code is the prudent course. If someone wanted to find an easy and safe way to make it only be triggered when the import fails, it could stay in. I'm not convinced that _anything_ in import.c is easy and safe. <wink> Anthony -- Anthony Baxter <anthony at interlink.com.au> It's never too late to have a happy childhood.
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