A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-December/107009.html below:

[Python-Dev] Column offsets for attribute nodes

[Python-Dev] Column offsets for attribute nodes [Python-Dev] Column offsets for attribute nodesSven Brauch svenbrauch at googlemail.com
Sun Dec 26 22:41:41 CET 2010
Hi there,

I recently filed a feature request in the tracker to change the
behaviour of the parser in terms of setting ranges on attribute AST
nodes, because I'm working on an application which needs more
information than is currently provided. I suggested to change the
behaviour from
foo.bar.baz # <- foo is said to start at column 0, bar at 0 and baz at
0 (current)
to
foo.bar.baz # <- foo starts at 0, bar at 3 and baz at 7 (suggestion)

In that discussion, there's been different opinions about which
behaviour is better; main arguments were "consistency" for the current
and "usefulness" for the suggested behaviour. It has been proposed to
ask the question on this list, that's why I'm doing that now. :)
The thread can be found here: http://bugs.python.org/issue10769

So, which version do you think to be better: the current one or the
suggested one?

Best regards,
Sven
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4