On 06 décembre 10:38, 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?
because pylint isn't expected to change your own code. > 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? astng may be used to write down python code, though it will be tricky to deal with formatting (spaces, eol, comments...). -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
