Discussion:
[Bitpim-devel] Some pychecker issues in calendarentryeditor
Roger Binns
2004-12-24 17:31:06 UTC
Permalink
calendarentryeditor.py:205: Local variable (field) not used
calendarentryeditor.py:239: No global (n) found
calendarentryeditor.py:289: Parameter (entry) not used
calendarentryeditor.py:591: No class attribute (fields) found
calendarentryeditor.py:592: No class attribute (fields) found

Roger
d***@netzero.com
2004-12-24 17:49:55 UTC
Permalink
Post by Roger Binns
calendarentryeditor.py:289: Parameter (entry) not used
What's the best way to make pychecker happy with unused parameters, aside from 'tmp=entry'

-Joe Pham


________________________________________________________________
NetZero Gift Certificates
Give the gift of Internet access this holiday season.
http://www.netzero.com/give
Roger Binns
2004-12-24 18:20:19 UTC
Permalink
Post by d***@netzero.com
Post by Roger Binns
calendarentryeditor.py:289: Parameter (entry) not used
What's the best way to make pychecker happy with unused parameters, aside from 'tmp=entry'
Give it the name of underscore _

It is more important to optimise your code for human readers rather
than software reading. If the name is important, or indicates
future work then leave it being something meaningful.

If you had to have a name for whatever reason and really don't care
about it then change it to underscore.

You probably noticed the huge amount of noise pycheck generates,
not to mention the bugs, so don't worry except about actual issues.

sf.net/tracker/?func=detail&aid=922154&group_id=24686&atid=382217
sf.net/tracker/?func=detail&aid=844960&group_id=24686&atid=382217
sf.net/tracker/?func=detail&aid=708546&group_id=24686&atid=382217

Roger

Loading...