Python parser ranges

[Niko Sams]

On Sat, Dec 25, 2010 at 16:37, Sven Brauch <svenbrauch at googlemail.com> wrote:
> Hi,
>
> the python parser is cool, but it doesn't give me quite all the range
> information I need. Sometimes, it just gives pointless crap (like, for
> foo.bar.baz it tells me that the column offset for baz is 0).
> This is easy to fix in the python parser (it's like removing 2 lines),
> but it doesn't look like they would change that (see
> http://bugs.python.org/issue10769).
> If I want to do this in the plugin, it's terribly complicated, as I
> kind of have to write my own lexer and stuff... Alternatively, I could
> fork the python parser, as it's really only two lines which need to be
> changed...
>
> What would you recommend?
>
I didn't follow the recent developments in python support, could you
write just a few lines
how this all works?

In theory I would prefer a fork that changes only very little code and
so can easily get updated
over some custom code that has to be maintained completely by ourselves.

Niko