are available in MacOS API exceptions.

type.__module__ problems (again?)

This simply initializes the __module__ local in a class statement from
the __name__ global.  I'm not 100% sure that this is the correct fix,
although it usually does the right thing.  The problem is that if the
class statement executes in a custom namespace, the __name__ global
may be taken from __builtins__, in which case it would have the value
__builtin__, or it may not exist at all (if the custom namespace also
has a custom __builtins__), in which case the class statement will
fail.

Nevertheless, unless someone finds a better solution, this is a 2.2.1
bugfix too.

on a function pointer formal argument called "destructor", which is typedeffed
as a different function pointer type in object.h.

new.instancemethod() -- the instancemethod object is now a perfectly
general container.

This fixes SF bug ##503091 (Pedro Rodriquez): new.instancemethod fails
for new classes

This is a 2.2.1 candidate.

be tested regardless of the host platform.

Fixed to work under MachoPython, doing the expected unpacking for applesingle files. The IDE still doesn't work, though, because it uses :-style pathnames.

In MachoPython expect Unix-style pathnames for both FSSpec and FSRef initializers. TBD: Do the reverse for MacPython, and also handle as_pathname().

headers and libraries.

- Use waste included with CW in stead of separate package.

Fixes #500595.

Added the modules I missed first time around. Still not good enough, though: bgerror does a "package require msgcat" and I don't see a way to put packages into resources. Off to the mactcl list for help...

going through the buffer interface API.

Added tests for this to the _testcapi module and updated docs.

that were changed but not yet reflected in this document.

os.system().
This closes Python bug #500401, Debian bug #127507.

Unicode string snippets to larger Unicode strings.

This fix should also go into Python 2.2.1.