If you've been reading pypy-svn you'll know I've written an import analysis tool (pypy/tool/importfun.py). While its implementation is currently completely inscrutable, here's some of its results. There are currently 242 import cycles in PyPy :(: http://starship.python.net/crew/mwh/importcycles.txt A 'summary' function gave this: the average module was imported 4.40 times imported 5.68 other modules defined 14.17 names there were 49 import *s the average one produced 5.33 names that were actually used Tests and tools aside, we have very few modules that aren't imported anywhere -- at least we're not too bad on this front :) And here's an analysis of the import *s in the code base (excluding tests, roughly speaking): http://starship.python.net/crew/mwh/importstar.txt Cheers, mwh -- <sjj> dash: you certainly are an enigma wrapped in a riddle wrapped in a hat. -- from Twisted.Quotes
Hi, On Thu, Oct 27, 2005 at 07:39:32PM +0100, Michael Hudson wrote:
If you've been reading pypy-svn you'll know I've written an import analysis tool (pypy/tool/importfun.py). While its implementation is currently completely inscrutable, here's some of its results.
Michael, if you are jumping into code-base analysis of PyPy, I suggest you give a try to pylint and maybe define a config file for pylint that would be in accordance with pypy's coding standard. -- Nicolas Chauvat logilab.fr - services en informatique avancée et gestion de connaissances
participants (2)
-
Michael Hudson -
Nicolas Chauvat