added notes about weakref changes

diff --git a/Misc/NEWS b/Misc/NEWS
index 9d2e3548756bad7eb351b811b2cf4f903ced68e1..f7f6ffbb02cc2b29e2892491d32c45028e2d3e30 100644 (file)
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -12,6 +12,21 @@ What's New in Python 2.4 alpha 1?
 Core and builtins
 -----------------
 
+- Made omitted callback and None equivalent for weakref.ref() and
+  weakref.proxy(); the None case wasn't handled correctly in all
+  cases.
+
+- Fixed problem where PyWeakref_NewRef() and PyWeakref_NewProxy()
+  assumed that initial existing entries in an object's weakref list
+  would not be removed while allocating a new weakref object.  Since
+  GC could be invoked at that time, however, that assumption was
+  invalid.  In a truly obscure case of GC being triggered during
+  creation for a new weakref object for an referent which already
+  has a weakref without a callback which is only referenced from
+  cyclic trash, a memory error can occur.  This consistently created a
+  segfault in a debug build, but provided less predictable behavior in
+  a release build.
+
 - input() builtin function now respects compiler flags such as
   __future__ statements.  SF patch 876178.