uses _DummyMutex on platforms without threads.

TemproraryFileWrapper wrapper anymore, and should be immune from the
problem that a temp file inherited by a spawned process caused an
attempt to close the temp file in the spawning process to blow
up (the unlink in TemporaryFileWrapper.close() blew up with a
"Permission denied" error because, despite that the temp file got
closed in the spawning process, the spawned process still had it open
by virtue of C-level file descriptor inheritance).  In context,
that bug took days to figure out <wink/sigh>.

NOTE:  this seems a mess wrt which symbols are available on which
platforms.  I can't fix it, but I didn't add to it <wink>, and
included an XXX comment about names claimed to be available on
Windows that aren't.  If anyone can figure out the whole ugly truth,
I'm sure a better organization will suggest itself.

completely determined by the example; dict insertion order and the string
hash algorithm no longer affect the output.
This fixes SF bug #509281.

This is an ancient race when multiple threads call gettempdir() (or
anything relying on it) for the first time.

Fixed x-platform via the Big Hammer of rearranging the code to serialize
the first calls.  Subsequent calls are as fast as before.

Note that the Python test suite can't provoke this bug:  it requires
setting up multiple threads making the very first calls into tempfile,
but the test suite uses tempfile several times before getting to
test_threadedtempfile.

Bugfix candidate.

#509074.

subpart.

with only one subpart.

that the first subpart added makes the payload a list object.
Otherwise, a multipart/* with only one subpart will not have the
proper structure.

2.2.1 bugfix candidate.

Fixes #505453.

Library Reference.

reports it doesn't exist anymore under .NET.

routine start() calling it.

Some suites declare an event start(), which obscures this method, which
causes the class initializer to fail when called with start=1.

Based on bug report and fix suggestion by Jacob Kaplan-Moss.

Bugfix candidate:  the current state of AutoIdent.py should be in 2.2.1.

[ #496154 ] Typos in dynload_beos.c

as suggested in the report.  A little embarassing; 2.2.1 candidate for sure.

indent error

Use // where int division is intended.  (This breaks IDLE for use with
previous Python versions -- I don't care.)

[ #433775 ] module build dir first in test import

though not in the way the summary would suggest; use imp.load_dynamic()
in setup.py to ensure we're testing the dynamic object we think we are.

so I threw reindent.py at it and look what happened!

Did setup.py escape Tim's regular whitespace normalizations?

borrowed references.

thanks Tim!