Use a slightly different strategy to determine when not to call the line
trace function. This removes the need for the RETURN_NONE opcode, so
that's gone again. Update docs and comments to match.
Thanks to Neal and Armin!
Also add a test suite. This should have come with the original patch...
[ 587993 ] SET_LINENO killer
Remove SET_LINENO. Tracing is now supported by inspecting co_lnotab.
Many sundry changes to document and adapt to this change.
Add new opcodes LOAD_CLOSURE, LOAD_DEREF, STORE_DEREF, MAKE_CLOSURE to
docs for dis module.
Add docs for new function and code members in Sec. 3 of ref manual.
They're present regardless of whether nested scopes are used.
Remove description of default argument hack from Sec. 7 of the ref
manual and refer the reader to the appendix.
name as n'. By doing some twists and turns, "as" is not a reserved word.
There is a slight change in semantics for 'from module import name' (it will
now honour the 'global' keyword) but only in cases that are explicitly
undocumented.
did the same anyway.
I'm not sure what to do with Tools/compiler/compiler/* -- that isn't part of
distutils, is it ? Should it try to be compatible with old bytecode version ?
checkin of myformat.sty.
Change "\renewcommand{\indexsubitem}{(...)}" to "\setindexsubitem{(...)}"
everywhere.
Some other minor nits that I happened to come across.
Removed the large comment remaining from the template documentation
section; the template tells us to remove these once they're not needed.
Remove some trailing whitespace from VM instruction pseudo-code.
to use the opcodedesc environment.
Changed a \code{} to a \file{} near the start where a file is referenced.
Fixed a typo: "on" --> "one" in ROT_THREE description.
Wherever opcodes were referenced by name, use \code{OPCODE_NAME}; usage was
inconsistent. Ideally, another macro would be defined since these don't
represent code a programmer would type, but that's minor even for me. It'll
probably get converted automatically in the SGML conversion project. Whether
that matters or not isn't relevant at this point.