over SEP, ALTSEP and MAXPATHLEN.
Patched up posixmodule.c for MSVC, but unsure what the story is now on
other non-Unixish platforms -- the preprocessor maze has no exit <wink>.

2.2.1 candidate (but not terribly important).

- recognize "SyntaxError"s by the print_file_and_line attribute.
- add the syntaxerror attributes to all exceptions in compile.c.
Fixes #221791

when no arguments are passed

(see patch #514490, by Stefan Schwarzer)

  Modules/
    posixmodule.c

- use SEP,ALTSEP #defines instead of hard coded path separator chars
- use EMX specific variants of chdir2(),getcwd() that support drive letters
- OS/2+EMX spawnv(),spawnve() support
- EMX specific popen[234]() derived from Win32 popen[234]() code

  Modules/
    socketmodule.c

EMX handles sockets like Posix, rather than use native APIs

  Modules/
    _hotshot.c
    dbmmodule.c
    fcntlmodule.c
    main.c
    pwdmodule.c
    readline.c
    selectmodule.c
    signalmodule.c
    termios.c
    timemodule.c
    unicodedata.c

platform realloc(p, 0) returns NULL, so MALLOC_ZERO_RETURNS_NULL can
be correctly undefined yet realloc(p, 0) can return NULL anyway.

Prevent realloc(p, 0) doing free(p) and returning NULL via a different
hack.  Would probably be better to get rid of MALLOC_ZERO_RETURNS_NULL
entirely.

Bugfix candidate.

dynamic theme changes

instead of faking it by hand.  It *is* a var object, and nothing but
hysterical raisins to pretend it's an oddball.

copy the sign too.  Added a test to test_descr to ensure that it does.

Bugfix candidate.

to fix was almost certainly a bug in _PyLong_Copy (which I'll fix next).

section use this class instead of UnixMailbox as per the comments in
the latter's class.

Bug fix candidate for 2.2.1.

Due to the bizarre definition of _PyLong_Copy(), creating an instance
of a subclass of long with a negative value could cause core dumps
later on.  Unfortunately it looks like the behavior of _PyLong_Copy()
is quite intentional, so the fix is more work than feels comfortable.

This fix is almost, but not quite, the code that Naofumi Honda added;
in addition, I added a test case.

Support GMP version >= 2.

Bugfix candidate.

discussed on python-dev.

- make array.array a type
- add Py_UNICODE arrays
- support +=, *=

Noted by Jason Orendorff, SF #520768.

Bug fix candidate for 2.1 & 2.2.

rexec.

When using a restricted environment, imports of copy will fail with an
AttributeError when trying to access types.CodeType.

Bugfix candidate (all the way back to 1.5.3, but at least 2.1.3 and
2.2.1).

A file-static "threads" dict mapped thread IDs to Windows handles, but
was never referenced, and entries never got removed.  This gets rid of
the YAGNI-dict entirely.
Bugfix candidate.

alignment gimmick.  David Abrahams notes that the standard "long double"
actually requires stricter alignment than "double" on some Tru64 box.
On my box and yours <wink>, it's the same, so no harm done on most
boxes.

Use posixly correct sort args.

Bugfix candidate.

- Use substring search, not re search for user-agent and paths.
- Consider * entry last. Unquote, then requote URLs.
- Treat empty Disallow as "allow everything".
Add test cases. Fixes #523041

  Objects/
    stringobject.c
    unicodeobject.c

bug #521526.

Doc/README is odd; it assigns some copyright to the PSF in 2000, when
I didn't think it existed...

There were never tests for the fact that list() always returns a *new*
list object, even when the argument is a list, while tuple() may
return a reference to the argument when it is a tuple.  Now there are.