Re: Highlighting program variables instead of keywords?

References	<CANc-5UwcZT18RgLqzHq0oMPA4sxfbfu0ZQhGPJBYZ0KEUJ6m2g@mail.gmail.com> <CANc-5UwkLjmwA5LCAKRGjDZaf5EiHXCfU4_Hm2e9yXsDmApR=g@mail.gmail.com> <CANc-5UxqBJPjk-QYgOL+n1A85xHAicPQHSPfB1fhBg877g0TTQ@mail.gmail.com> <lc4a8n$982$1@ger.gmane.org>
Date	2014-01-26 19:46 -0600
Subject	Re: Highlighting program variables instead of keywords?
From	Skip Montanaro <skip@pobox.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.6013.1390787615.18130.python-list@python.org> (permalink)

Show all headers | View raw

> What it is doing is color coding user-supplied identifiers, with different
> color for each one. I found that confusing to read.

I think it would take some time to get used to, and I don't think it
would be the only way I'd like to view my program.

I think an interactive pylint (or pyflakes or frosty) type capability
would be useful, highlighting a subset of the messages it produces,
like variables which were assigned but never used, or using undefined
variables. It might be best supported by actually running the checker
in the background, then using its messages to direct where to
highlight suspect bits of code.

Skip

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Highlighting program variables instead of keywords? Skip Montanaro <skip@pobox.com> - 2014-01-26 19:46 -0600

csiph-web