On Monday 23 November 2009 22:46:43 Ian Eure wrote: > I've hit a couple cases in PyLint where it goes into an infinite loop. In > one of these cases, I was able to narrow it down to the line which > triggers the loop, though I couldn't come up with a simple testcase. The > source I'm running PyLint on is not public.
A good start is * subscribing to the mailing list by visiting http://lists.logilab.org/mailman/listinfo/python-projects * giving us the output of pylint --version Then, even if your source is not public, maybe you can provide some information such as a stack trace (if the loop is a recursion, you have one, if not, try hitting ctrl-C to generate a KeyboardInterrupt exception). Once you know where the looping happens, instrumenting the pylint code in the looping function(s) can help understanding what's wrong. As Sylvain said, tomorrow is Pylint Bug day, and there will be people on irc to help you diagnose this. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science _______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
