On Sun, Aug 17, 2008 at 1:40 PM, Georg Brandl <[EMAIL PROTECTED]> wrote: > Brett Cannon schrieb: >> After Christian mentioned how we could speed up interpreter start-up >> by removing some dead imports he found, I decided to write up a quick >> script that generates the AST for a source file and (very roughly) >> tries to find imports that are never used. People think it's worth >> tossing into Tools, even if it is kind of rough? Otherwise I might >> toss it into the sandbox or make a quick Google code project out of >> it. >> >> Regardless, one interesting side-effect of the script is that beyond >> finding some extraneous imports in various places, it also found some >> holes in __all__. I have the script look for the definition of __all__ >> and consider an import used if it is listed there. > > pylint already finds unused imports. It finds tons of other, relatively > useless, stuff in the default configuration, but I'm sure it can be > coaxed into only showing unused imports too. >
Does anyone ever run pylint over the stdlib on occasion? -Brett _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
