Completely untested.

by request of Donovan Preston. In return, he promised to use this
to create a Python OSA component, which would turn Python
into a first-class OSA scripting language (like AppleScript itself).

by setting TESTFN_UNICODE_UNENCODEABLE on these platforms.
test_unicode_file only attempts to use the name for testing if not None.

and pass them along to the PrettyPrinter constructor.

and dict too, as long as they don't overwrite __repr__().

for Big String).  This should make the tests pass on Win98SE.  Note
that the docs only promise lengths up to 2048.  Unfortunately this no
longer tests for the segfault I was seeing earlier, but I'm confident
I've nailed that one. :-)  Fixes SF 852281.  Will backport to 2.3.

unicode filenames"
Reorganize tests into functions so more combinations of
unicode/encoded/ascii can be tested, and while I was at it, upgrade to
unittest based test.

encoded using the default file system encoding.

implement its locking scheme, this module implements a crude link() by
way of copying the source to the destination provided the destination
doesn't already exist.

library search path to include the extension directory.  Without this,
the curses_panel extension can't find the curses extension/DLL, which
exports some curses symbols to it.

- various minor cleanups and updates.

  a Python extension, so that the curses_panel extension works.
- minor compiler switch tweak.

Use a set instead of dict with values equal to one.

comments about why both calls to cyclic gc here can cause problems.

I'll backport to 2.3 maint.  Since the calls were introduced in 2.3,
that will be the end of it.

Backported to 2.3.

operator module.

isn't checked, and it *is* possible that a very large alloca() call is
made, e.g. when a large registry value is being read.  I don't know if
alloca() in that case returns NULL or returns a pointer pointing outside
the stack, and I don't want to know -- I've simply replaced all calls to
alloca() with either PyMem_Malloc() or PyString_FromStringAndSize(NULL,)
as appropriate, followed by a size check.  This addresses SF buf 851056.
Will backport to 2.3 next.

2**32-1 makes no sense.  Use 2**31-1 instead.

  and left shifts.  (Thanks to Kalle Svensson for SF patch 849227.)
  This addresses most of the remaining semantic changes promised by
  PEP 237, except for repr() of a long, which still shows the trailing
  'L'.  The PEP appears to promise warnings for operations that
  changed semantics compared to Python 2.3, but this is not
  implemented; we've suffered through enough warnings related to
  hex/oct literals and I think it's best to be silent now.

an exception raised by the key function.
(Suggested by Michael Hudson.)

is installed but the registry settings are incomplete because the gui
has never been run.

Already backported to release23-maint.

cause an index error. We now select the first package if this threatens
to happen. Will backport.

confusing. To be on the safe side we always show hidden packages before
showing error dialogs. Will backport.

Things will definitely change before 2.4, but for now use a slightly
different URL.