[Python-Dev] ImportWarning flood (original) (raw)
Guido van Rossum guido at python.org
Sat Jul 1 04:55:03 CEST 2006
- Previous message: [Python-Dev] 2.5 and beyond
- Next message: [Python-Dev] ImportWarning flood
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. ;-)
--Guido (ducks)
On 6/30/06, Shane Hathaway <shane at hathawaymix.org> wrote:
Guido van Rossum wrote: > On 6/30/06, Jean-Paul Calderone <exarkun at divmod.com> wrote: >> How about if someone grovels through import.c and figures out how to make >> the warning information only show up if the import actually fails? > > That would work I think. But it's not easy.
I just posted a patch intended to solve this. With my patch, findmodule() collects the warnings in a list and only generates ImportWarning if no package is found. It works, but I have not done extensive testing. I also discovered and tried to resolve what appear to be memory leaks involving the "copy" variable. If the ImportWarning patch doesn't fly, I'll be happy to post a different patch that only fixes the leaks. The patch is #1515361: https://sourceforge.net/tracker/index.php?func=detail&aid=1515361&groupid=5470&atid=305470 Shane
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] 2.5 and beyond
- Next message: [Python-Dev] ImportWarning flood
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]