Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #64859 > unrolled thread

Re: Highlighting program variables instead of keywords?

Started byMark Lawrence <breamoreboy@yahoo.co.uk>
First post2014-01-27 13:38 +0000
Last post2014-01-27 13:38 +0000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Highlighting program variables instead of keywords? Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-01-27 13:38 +0000

#64859 — Re: Highlighting program variables instead of keywords?

FromMark Lawrence <breamoreboy@yahoo.co.uk>
Date2014-01-27 13:38 +0000
SubjectRe: Highlighting program variables instead of keywords?
Message-ID<mailman.6039.1390830006.18130.python-list@python.org>
On 27/01/2014 01:46, Skip Montanaro wrote:
>> 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
>

Pydev uses pylint interactively, must have saved me hours by flagging up 
(potential) problems up as I type.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web