pre-increment forms to post-increment forms.  Post-incrementing
also eliminates the need for negative array indices for oparg fetches.

* In exception handling code, check for class based exceptions before
  the older string based exceptions.

BINARY_SUBSCR:
    * invert test for normal case fall through
    * eliminate err handling code by jumping to slow_case

LOAD_LOCALS:
    * invert test for normal case fall through
    * continue instead of break for the non-error case

STORE_NAME and DELETE_NAME:
    * invert test for normal case fall through

LOAD_NAME:
    * continue instead of break for the non-error case

DELETE_FAST:
    * invert test for normal case fall through

LOAD_DEREF:
    * invert test for normal case fall through
    * continue instead of break for the non-error case

Restores the self-documenting enum declaration.

This allows multiple flags to be tested in a single compare
which eliminates unnecessary compares and saves a few bytes.

been used. (Suggested by Martin v. Loewis)

tests of "why" against WHY_YIELD became useless.  This patch removes them,
but assert()s that why != WHY_YIELD everywhere such a test was removed.
The test suite ran fine under a debug build (i.e., the asserts never
triggered).

attribute name lookup.

the socket name must start with /socket32/.  Unlike Unix systems, this
file never exists in the file system.

with major C compilers (VACPP, EMX+gcc and [Open]Watcom).

Also tidy up the export of spawn*() symbols in the os module to match what
is found/implemented.

close() calls would attempt to free() the buffer already free()ed on
the first close().     [bug introduced with patch #788249]

Making sure that the buffer is free()ed in file object deallocation is
a belt-n-braces bit of insurance against a memory leak.

Also, move pystack comment down next to it

as directly setting the .prog attribute (which should be supported based on
the class docstring).
Closes SF bug #850964.

Revise the long comment that explained details of the magic number
in gory detail.

[Bugfix candidate] Escape traceback type and value.  There are probably additional cases where cgitb.py doesn't escape as paranoidly as it should (e.g. attribute names)

Backported to 2.3.

inherit those bits, causing the test_mkdtemp.test_mode() test to fail.
Remove those before comparing the actual mode to the expected mode.

PDF and PostScript versions of the docs (the CSS already does this for HTML)

Closes SF bug #837228; backporting for Python 2.3.4.

distribution (see SF bug #796042)

member.

The .closed property always returned the wrong result.

Bugfix candidate!

- fix a couple typos
- refine definitions for "interpreted" and "coercion" based upon updates on
  the python glossary wiki

* Factor constant expressions out of loops.
* Presize a list being grown to a known length.

version of Tcl other than ActiveTcl is installed (ActiveTcl
included TclX, other Tcl distros didn't).

I'm removing the package loading test because it's hard to
come up with a package that is guaranteed to be in any Tcl installation.

Special-casing darwin and windows is ok since that leaves the
only Tk platform (X) which the test was trying to address.

* pre-build a single identity function for the fixup function
* pre-build membership tests in dictionaries instead of in-line tuples
* assign len() to a local variable
* assign append() methods to a local variable
* use xrange() instead of range()
* replace "x<<1" with "x+x"