Re: Highlighting program variables instead of keywords?

From	Terry Reedy <tjreedy@udel.edu>
Subject	Re: Highlighting program variables instead of keywords?
Date	2014-01-27 01:37 -0500
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> <CANc-5UwA-N4-FUivgd3yGsquDcTAa+LWJs5ewoeW8nTgW+LQ9Q@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.6024.1390804640.18130.python-list@python.org> (permalink)

Show all headers | View raw

On 1/26/2014 8:46 PM, Skip Montanaro wrote:

> 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.

One of my long-term goals for Idle is an extension that would run 
user-installed code analyzers over the contents of an edit window, with 
the output sent to an OutputWindow. Using the contents of the latter to 
mark things in the editor window is an interesting idea. That is already 
done for SyntaxErrors and traceback file:line references.

-- 
Terry Jan Reedy

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

Thread

Re: Highlighting program variables instead of keywords? Terry Reedy <tjreedy@udel.edu> - 2014-01-27 01:37 -0500

csiph-web