If the initial import of warnings fails, clear the error.  When the module
is actually needed, if the original import failed, see if it has managed
to find its way to sys.modules yet and if so, remember it.

text.  There needs to be a better way.

  - fix comment describing what this is for
  - add lots of indexing macros to this call
Closes SF bug #518989.

Pertains to SF bug #518989.

Checking // would call floor division but did not test that
true division had become the default with 'from __future__ import division'.

Checking // would call floor division but did not test that
true division had become the default with 'from __future__ import division'.

Closes SF bug #453683.

Bug fix candidate.

Fixes for three related bugs, including errors that caused a script to
be ignored without printing an error message.  The key problem was a bad
interaction between syntax warnings and syntax errors.  If an
exception was already set when a warning was issued, the warning could
clobber the exception.

The PyErr_Occurred() check in issue_warning() isn't entirely
satisfying (the caller should know whether there was already an
error), but a better solution isn't immediately obvious.

Bug fix candidate.

[Patch #708374] Only apply the check for file size if the file is a regular file, not a character or block device.

"print repr(proxy(a))" and "proxy(a)" at an interactive prompt.
Closes SF bug #722763.

- wrap some long lines
- shorten others
- fix indentation

database corruption problems with Spambayes.

                amendment

Add a clarifying cross-reference to the formatter module.

(Contributed by Andrew I MacIntyre.)

(contributed by Vincent Delft.)

The script updated os.environ but failed to pass the whole environment
to the child process (the CGI script).

closing idempotent (it used to raise a nuisance exception on the 2nd
close attempt).

Bugfix candidate?  Probably, but arguable.

(Contributed by George Yoshida.)

- separate the building of the core from the wrapper executables and the
  external modules (.PYDs), based on the Py_BUILD_CORE define;

- clean up the generated import library definiton (.DEF file) to remove
  references to a number of non-static symbols that aren't part of the
  Python API and which shouldn't be exported by the core DLL;

- compile the release build with -fomit-frame-pointer, for a small
  performance gain;

- make "make clean" remove byte compiled Python library files.

Needs to be backported to both IDLE and IDLEFORK.

* It ran fine under "python regrtest.py test_warnings" but failed under
  "python regrtest.py" presumably because other tests would add to
  filtered warnings and not reset them at the end of the test.

* Converted to a unittest format for better control.  Renamed
  monkey() and unmonkey() to setUp() and tearDown().

* Increased coverage by testing all warnings in __builtin__.

* Increased coverage by testing regex matching of specific messages.

reported consistently with the *nix world.  'Lib/test/test_warnings.py'
came out as 'lib\test\test_warnings.py'.  The basename is all we care
about so I used that.

Related to SF patch 723231 (which pointed out the problem, but didn't
fix it, just shut up the warning msg -- which was pointing out a dead-
serious bug!).

Bugfix candidate.