On 15 juin 10:23, John Fawcett wrote: > Hi, Hi,
> I was wondering if you have considered adding column offsets to your message > information? I've been working on a really simple IDE that uses pylint to > find problems and then highlight the code (red-squiggly like spellcheck). It > would be really useful to receive more information about the location of an > error. Looking through the astng code, it looks as though offsets are not > tracked at all, so this would be a pretty low-level addition. If you think > about integrating pylint output with IDEs, more fine-grained location > information is a huge value. I hope you can consider making this addition. ASTNG is using the python ast representation as basis. A don't think there is such column offset information there. Either I'm wrong, then we could easily have a pylint reporter that display this information, or I'm right, and this should be added as a feature request for python itself. IMO that would be a pain to do this by ourself. -- 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
