Your message dated Sat, 9 Aug 2014 16:40:14 +0100
with message-id
<cab4xwxw8ydwpcpjo56oe7+sg2ugqhqdabs0rwgyyo_qrzyu...@mail.gmail.com>
and subject line Re: pylint: Pylint needs to be more accessible to new users
has caused the Debian Bug report #466385,
regarding pylint: Pylint needs to be more accessible to new users
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
466385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466385
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pylint
Version: 0.13.2-2
Severity: wishlist
The initial use of pylint is likely to drown the user in dozens or
hundreds of messages about violated coding conventions.
More important warnings cannot be found amongst this chaff.
(Not that I'm really against coding conventions, but badly named
variables are not errors: they are merely things that may cause
confusion in the programmer, which then might lead to an error.)
>> Many other users are doubtless in the same boat. ...
>> It is a behavior of the program that is serious enoug to keep it from being
>> used.
>> (And don't claim that it doesn't bother *you*: that's irrelevant.
>> Developers of a program are hardly normal users of it!)
>
> It does bother us, and that's precisely why we wrote pylint in the first
> place : so that it would bother us and put us in a mood to either
> explain pylint what the coding conventions of a given project are, or
> use the default coding convention. As a result out code does not suffer
> a lot of those warnings (try running "pylint pylint" for example).
Yeah, but you're not taking the viewpoint of a new user.
A new user doesn't know if pylint is any good or not.
His or her first desire is to find out "Is this going to help me?"
If he or she can't tell -- because the juicy output is hidden amongst
a lot of low-priority stuff about naming conventions --
there is a strong temptation to say
"Oh, sod it. I'll try pychecker instead. sudo apt-get remove pylint"
You need to *convince* the new user that pylint is worth spending time on.
Unlike you, the new user has no commitment to using pylint.
With apt-get, it's easy come and easy go with only 1 minute of
experimentation in between. You need pylint to prove its value
in that single minute.
Or finally, put a counter in so that pylint (by default) will only
display the first 10 errors/warnings in each category. That way,
if you run pylint on code that follows different coding conventions,
you won't drown.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages pylint depends on:
ii python 2.4.4-6 An interactive high-level object-o
ii python-logilab-astng 0.17.1-1 extend python's abstract syntax tr
ii python-logilab-common 0.22.2-1 useful miscellaneous modules used
Versions of packages pylint recommends:
ii python-tk 2.4.4-3 Tkinter - Writing Tk applications
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
this bug has been forwarded to upstream for over 6 years and nothing
has moved since that far, i guess that if you want to pursue your
objective you'd better talk to upstream directly. Thus im closing this
bug.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
