By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,694 Members | 1,882 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,694 IT Pros & Developers. It's quick & easy.

Nitpicking - slightly misleading traceback

P: n/a
if ((data[x][y] > 0) or
(datadict.has_key[key])):

Traceback (most recent call last):
File "reduce.py", line 524, in remove_badvalues
if ((data[x][y] > 0) or
TypeError: unsubscriptable object

However, the bug sits on the next line. I used square brackets when
normal brackets were needed - should have written datadict.has_key(key)
as the old code had datadict[key]. In the real code variable names are
so long that I must split the line. I feel the traceback is misleading.

I guess the best solution is to write code without bugs...
Jan 26 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Juho Schultz enlightened us with:
However, the bug sits on the next line. [...] I feel the traceback
is misleading.


Well, the bug sits in the command starting on the line indicated.

Nitpick back: Learn about operator precedence and Python syntax rules.
You don't need so many brackets:

if data[x][y] > 0 or datadict.has_key(key):

This might even make things fit on one line again ;-)

Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?
Frank Zappa
Jan 26 '06 #2

P: n/a
Sybren Stuvel <sy*******@YOURthirdtower.com.imagination> wrote:
...
if data[x][y] > 0 or datadict.has_key(key):

This might even make things fit on one line again ;-)


Particularly if you code it idiomatically:

if data[x][y] > 0 or key in datadict:
Alex
Jan 26 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.