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


Groups > comp.lang.python.announce > #2768 > unrolled thread

locstacktrace 1.0.0 - More precise stack traces

Started byRocky Bernstein <rb@dustyfeet.com>
First post2018-02-17 19:07 -0500
Last post2018-02-17 19:07 -0500
Articles 1 — 1 participant

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

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

  locstacktrace 1.0.0 - More precise stack traces Rocky Bernstein <rb@dustyfeet.com> - 2018-02-17 19:07 -0500

#2768 — locstacktrace 1.0.0 - More precise stack traces

FromRocky Bernstein <rb@dustyfeet.com>
Date2018-02-17 19:07 -0500
Subjectlocstacktrace 1.0.0 - More precise stack traces
Message-ID<mailman.48.1519045284.2791.python-announce-list@python.org>
Want to see more precisely where you are or were at in a traceback or
callstack your Python code has several places in a line it could have
errored ? Even if the code was something created at runtime with say
`eval` or `exec` or there is otherwise no source code?

Then this package is for you.

Some examples of the kinds of code this module can disambiguate:



   i / j / k                              # which divide?
   prev[prev[0]]                          # which prev ?
   [e[0] for i in d[j] if got[i] == e[i]] # lots going on here
   exec(some_code % 10, namespace)        # code at runtime

[toc] | [standalone]


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


csiph-web