Re: How to read and post tracebacks (was Registry Key Value Help)

References	<CAJ+TeocRV3+8v-5zMGO9vmDKr5jSFt2jkrD4q5c2QuT_oxyeHg@mail.gmail.com>
Date	2014-01-03 15:03 +1100
Subject	Re: How to read and post tracebacks (was Registry Key Value Help)
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.4826.1388721841.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Fri, Jan 3, 2014 at 2:58 PM, Rustom Mody <rustompmody@gmail.com> wrote:
> Why not write up a few lines on "How to read and post python tracebacks"
> and post it on the wiki?

You mean "copy and paste the whole output"? I'm not sure what more
needs to be said about posting them.

Reading them is a bit more complicated, but possibly _too_ complicated
for a simple wiki post. Being able to quickly eyeball a traceback and
know which level to look for the problem at is part of the skill of
debugging, and it usually requires that you know the codebase fairly
well too. Though even with unfamiliar code, it's possible to figure a
lot out by naming conventions, which is why they're so important (all
uppercase meaning "constant" and normally a scalar - so useful).

ChrisA

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: How to read and post tracebacks (was Registry Key Value Help) Chris Angelico <rosuav@gmail.com> - 2014-01-03 15:03 +1100
  Re: How to read and post tracebacks (was Registry Key Value Help) Roy Smith <roy@panix.com> - 2014-01-02 23:30 -0500

csiph-web