On Tuesday 06 December 2011 11:38:26 Andrea Crotti wrote: > Unless I missed something PyLint only checks and notifies for problems. > Now I would like to investigate if it's possible to write some "solvers" > for these problems. > > For example suppose you find an unused import, why not just delete it or > ask to delete > it interactively? > > From what I've understood is not so trivial because the analysis is > normally done on the > AST, and writing back code from the modified AST is not trivial, but do > you know > about any ways to tacke the problem?
IMO, this is an IDE's job to get information from Pylint and provide tools to modify the source code. Maybe you could try to integrate Pylint with rope ? http://rope.sourceforge.net/ -- 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 [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
