- remove text about the long-moved Mac OS libref chapter

The fix is confined to the Windows installer.

Not a bugfix candidate:  the need for the new -n switch added here was
introduced by moving to the idlefork IDLE (so this change isn't needed
or helpful before 2.3).

a wrong place over the weekend.

blurb about ZoneAlarm (etc) nags.

warnings from personal firewall software.  Added the same text
to README.txt, updated NEWS.txt for release.

M NEWS.txt
M PyShell.py
M README.txt

which is really important. This is a stopgap measure, as only the generated
C code is adapted. Fixes #776533.

LocaleTime instance to only be created once and thus not be recreated when
the locale changed.

Our saved locale was not being freed.  Also check correct variable for
NULL.

caught when executing test_strptime, test_logging, and test_time in that order
when the testing of "%c" occured.  Suspect the cache was not being recreated
(the test passed when test_logging was forced to re-establish the locale).

during the day tomorrow, so doing it earlier than I'd like.

This makes test_coercion pass on Panther.

Also added a note to NEWS that pythonw works again (it was broken in rc1).

   by patch 769142.  Fixed by patch 776062. KBK will backport net result
   to IDLE release22-maint and IDLEfork.
2. Update NEWS.txt and idlever for release.

Closes SF bug #776181.  Should be backported.

problems than it solves. In stead, put a warning near the top of the
welcome message. Fixes (or, rather works around) bug #764975.

to the name change of Python.app/Contents/MacOS/python to
Python.app/Contents/MacOS/Python. Fixes #776116.

all I know, the original locale may be '' (I don't think that's possible,
but ...), and if so we would certainly want to restore it.

Obtain the original locale in the documented way.  This way actually
works for me.

Restore the original locale at the end, instead of forcing to "C".

Move the locale fiddling into the test driver instead of doing it as a
side effect of merely importing the module.  I don't know why the test
is mucking with locale (and also added a comment saying so), but it
surely has no justification for doing that as an import side-effect.
Now whenever the locale-changing code executes, the locale-restoring code
will also get run.