https://hg.dopieralski.pl/cpython-lru_cache-weakref/ en-us Doc/c-api/code.rst revision history https://hg.dopieralski.pl/cpython-lru_cache-weakref/log/90f0dd118aa4/Doc/c-api/code.rst Eli Bendersky <eliben@gmail.com> Sun, 03 Jun 2012 08:07:47 +0300 https://hg.dopieralski.pl/cpython-lru_cache-weakref/log/b22a35c14a91/Doc/c-api/code.rst Meador Inge <meadori@gmail.com> Thu, 19 Jan 2012 22:06:31 -0600 https://hg.dopieralski.pl/cpython-lru_cache-weakref/log/9076e4220fa4/Doc/c-api/code.rst Georg Brandl <georg@python.org> Sat, 15 Jan 2011 17:03:02 +0000 https://hg.dopieralski.pl/cpython-lru_cache-weakref/log/521eac31a893/Doc/c-api/code.rst Georg Brandl <georg@python.org> Wed, 06 Oct 2010 10:11:56 +0000 https://hg.dopieralski.pl/cpython-lru_cache-weakref/log/79718ee03986/Doc/c-api/code.rst svn+ssh://pythondev@svn.python.org/python/trunk

........
r72487 | jeffrey.yasskin | 2009-05-08 17:51:06 -0400 (Fri, 08 May 2009) | 7 lines

PyCode_NewEmpty:
Most uses of PyCode_New found by http://www.google.com/codesearch?q=PyCode_New
are trying to build an empty code object, usually to put it in a dummy frame
object. This patch adds a PyCode_NewEmpty wrapper which lets the user specify
just the filename, function name, and first line number, instead of also
requiring lots of code internals.
........
r72488 | jeffrey.yasskin | 2009-05-08 18:23:21 -0400 (Fri, 08 May 2009) | 13 lines

Issue 5954, PyFrame_GetLineNumber:
Most uses of PyCode_Addr2Line
(http://www.google.com/codesearch?q=PyCode_Addr2Line) are just trying to get
the line number of a specified frame, but there's no way to do that directly.
Forcing people to go through the code object makes them know more about the
guts of the interpreter than they should need.

The remaining uses of PyCode_Addr2Line seem to be getting the line from a
traceback (for example,
http://www.google.com/codesearch/p?hl=en#u_9_nDrchrw/pygame-1.7.1release/src/base.c&q=PyCode_Addr2Line),
which is replaced by the tb_lineno field. So we may be able to deprecate
PyCode_Addr2Line entirely for external use.
........
r72879 | jeffrey.yasskin | 2009-05-23 19:23:01 -0400 (Sat, 23 May 2009) | 14 lines

Issue #6042:
lnotab-based tracing is very complicated and isn't documented very well. There
were at least 3 comment blocks purporting to document co_lnotab, and none did a
very good job. This patch unifies them into Objects/lnotab_notes.txt which
tries to completely capture the current state of affairs.

I also discovered that we've attached 2 layers of patches to the basic tracing
scheme. The first layer avoids jumping to instructions that don't start a line,
to avoid problems in if statements and while loops. The second layer
discovered that jumps backward do need to trace at instructions that don't
start a line, so it added extra lnotab entries for 'while' and 'for' loops, and
added a special case for backward jumps within the same line. I replaced these
patches by just treating forward and backward jumps differently.
........]]> Alexandre Vassalotti <alexandre@peadrop.com> Tue, 21 Jul 2009 04:30:03 +0000