Based on a patch from Hye-Shik Chang.

no "doc" argument given. This makes it possible to legitimately use
property() as a decorator to produce a read-only property.

module.

missing PyObject_Del()'s, simplify some code by using Py_BuildValue()
instead of creating a tuple with items manually, stop clobbering builtin
exceptions in a few places, and guard against NULL-returning functions some
more.

This fixes 117 of the 780 (!?!#%@#$!!) reference leaks in test_bsddb3. I
ain't not done yet, although this review of 5kloc was just the easy part.

an error code, this let `self` leak.  This is a disaster
on Windows, since `self` already points to a newly-opened
file object, and it was impossible for Python code to
close the thing since the only reference to it was in a
blob of leaked C memory.

test_hotshot test_bad_sys_path():  This new test provoked
the C bug above.  This test passed, but left an open
"@test" file behind, which caused a massive cascade of
bogus test failures in later, unrelated tests on Windows.
Changed the test code to remove the @test file it leaves
behind, which relies on the change above to close that
file first.

This was mostly written by Travis Oliphant.
I've inspected it all; Neal Norwitz and MvL have also looked at it
(in an earlier incarnation).

but an earlier line checked for v != NULL unnecessarily.

(reviewed by Neal Norwitz)

Normalize coding style.

Will backport.

Will backport to release24.

return rather than use it again.

readdir().

Add (int) casts to silence compiler warnings.
Raise Python exceptions for overflows.

added to gc.collect().  Updated docs, unit test, and NEWS entry.

(Also, fixed a typo in NEWS.)

All of these (except _lsprof.c) should be backported.  Particularly
the hotshot change which validates sys.path.  Can someone backport?

from static analysis.  v was already checked for NULL above, so we don't
need a second check.

This is a alternative version of patch #1379332.