How to pop the interpreter's stack?

kj no.email at please.post
Wed Dec 22 18:37:27 EST 2010


In <1f47c36d-a509-4d05-ba79-62b4a534bfe0 at j19g2000prh.googlegroups.com> Carl Banks <pavlovevidence at gmail.com> writes:

>On Dec 22, 8:52=A0am, kj <no.em... at please.post> wrote:
>> In <mailman.65.1292517591.6505.python-l... at python.org> Robert Kern <rober=
>t.k... at gmail.com> writes:
>>
>> >Obfuscating the location that an exception gets raised prevents a lot of
>> >debugging...
>>
>> The Python interpreter does a lot of that "obfuscation" already, and I
>> find the resulting tracebacks more useful for it.
>>
>> An error message is only useful to a given audience if that audience
>> can use the information in the message to modify what they are
>> doing to avoid the error.

>> =A0It is of no use (certainly no *immediate*
>> use) to this audience to see tracebacks that go deep into code that
>> they don't know anything about and cannot change.

>So when the audience files a bug report it's not useful for them to
>include the whole traceback?

Learn to read, buster.  I wrote *immediate* use.

~kj



More information about the Python-list mailing list