|
pylint #9774 some thoughts for simplifying the user interface [resolved]Some remarks for simplifying/improving pylint's user interface: imho, pylint should
- have a much shorter message on the '-h, --help' options, around 20 / 30 lines (the biggest part should be in the manpage)
- disable similarities checking by default for code of a given size
- maybe it would even be better not to produce a report by default (the important things are the messages, not the stats).
| | priority | normal |
|---|
| type | enhancement |
|---|
| appeared in | <not specified> |
|---|
| done in | 0.21.0 |
|---|
| load | 0.500 |
|---|
| load left | 0.000 |
|---|
| closed by | <not specified> |
|---|
Workflow history| from state (3) | to state | comment | date | User |
|---|
| validation pending | resolved | | 2010/08/26 10:18 | sthenault |
| done | validation pending |
version published
| 2010/05/11 15:29 | sthenault |
| open | done | considered as done by messages/reports options control unification
| 2010/04/20 08:03 | sthenault |
| |
|
Logilab.org 
[register] [login]
#9634 be smarter with vars() and locals()
Comments
-
2009/10/21 14:01, written by sthenault
| reply to this comment
(add comment)mads comment on the mailing-list about options...
In my opinion one important aspect of usability is "conceptual complexity". The names of these filtering options introduce the concept "message category". It is not obvious to me what that is, and thus I tend to ignore these options when I browse the list of options. And intuitively I think that when the option names are long then they must be for some advanced and seldom used functionality.
I wanted to check the help text where the user can find this option. The help text was so long and structured in a way which wasn't obvious to me as user that I gave up finding it with eye-grep. I ended up piping it through less, and fortunately I knew what to search for ... I suggest that the default help text only contains commonly used and important options - and especially not options for tweaking individual "checks".
I suggest that all the enable/disable options are merged to one enable/disable option which can control anything. I think it will be obvious from the parameter value what should be enabled/disabled.