From: Benjamin Peterson Date: Mon, 2 Mar 2015 01:59:22 +0000 (-0500) Subject: remove mention of Python 2.2 and 2.3 X-Git-Tag: v3.5.0a2~55^2 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6e820c0548671847d873f6550ed9e5e7eaaaef89;p=python remove mention of Python 2.2 and 2.3 --- diff --git a/Misc/SpecialBuilds.txt b/Misc/SpecialBuilds.txt index 732cb00178..3004174bcd 100644 --- a/Misc/SpecialBuilds.txt +++ b/Misc/SpecialBuilds.txt @@ -216,12 +216,11 @@ LLTRACE Compile in support for Low Level TRACE-ing of the main interpreter loop. -When this preprocessor symbol is defined, before PyEval_EvalFrame (eval_frame in -2.3 and 2.2, eval_code2 before that) executes a frame's code it checks the -frame's global namespace for a variable "__lltrace__". If such a variable is -found, mounds of information about what the interpreter is doing are sprayed to -stdout, such as every opcode and opcode argument and values pushed onto and -popped off the value stack. +When this preprocessor symbol is defined, before PyEval_EvalFrame executes a +frame's code it checks the frame's global namespace for a variable +"__lltrace__". If such a variable is found, mounds of information about what +the interpreter is doing are sprayed to stdout, such as every opcode and opcode +argument and values pushed onto and popped off the value stack. Not useful very often, but very useful when needed.