Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #64833 > unrolled thread
| Started by | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| First post | 2014-01-27 01:37 -0500 |
| Last post | 2014-01-27 01:37 -0500 |
| 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.
Re: Highlighting program variables instead of keywords? Terry Reedy <tjreedy@udel.edu> - 2014-01-27 01:37 -0500
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2014-01-27 01:37 -0500 |
| Subject | Re: Highlighting program variables instead of keywords? |
| Message-ID | <mailman.6024.1390804640.18130.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web