Hi, Thanks for the speedy reply. I'd love to write the patch!
I actually read most of the code yesterday, and I have to admit that I couldn't find any references to _ast -- could you give me a nudge in the right direction? thanks, fawce On Thu, Jun 16, 2011 at 7:40 AM, Sylvain Thénault < [email protected]> wrote: > On 16 juin 13:31, Amaury Forgeot d'Arc wrote: > > Hi, > > > > 2011/6/16 Sylvain Thénault <[email protected]>: > > > 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. > > > > Ast nodes do have column information: > > http://docs.python.org/library/ast.html#ast.AST.col_offset > > Duh, I missed this. Good to know. > > So it should be easy to write a patch so that this information get > back to pylint reporters, than to write a IDE dedicated reporter that > use this information. John, would you put ticket for this? Maybe provide > a patch as well :) > > -- > 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
