Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #63037 > unrolled thread

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

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: How to read and post tracebacks (was Registry Key Value Help) Rustom Mody <rustompmody@gmail.com> - 2014-01-03 10:46 +0530

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

On Fri, Jan 3, 2014 at 9:33 AM, Chris Angelico <rosuav@gmail.com> wrote:
> 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).

Something like this is what I had in mind
http://help.openerp.com/question/9704/how-to-read-and-understand-errors-from-tracebacks/

Obviously it can be written much better (and thought you could make a start :D)

[I wonder if the "please make it readable thus not thus" at end proves
or disproves Roy's point??]

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web