summaryrefslogtreecommitdiffstats
path: root/Misc
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2004-02-06 04:15:22 (GMT)
committerFred Drake <fdrake@acm.org>2004-02-06 04:15:22 (GMT)
commit228765b0e115b0534ca76d10c949afcb4bd50cdd (patch)
treef10d3608baaa986ae31eb6b9a5b643d55e6823b6 /Misc
parentd310f13cd2c321f0cca8429f611546c7888ae561 (diff)
downloadcpython-228765b0e115b0534ca76d10c949afcb4bd50cdd.zip
cpython-228765b0e115b0534ca76d10c949afcb4bd50cdd.tar.gz
cpython-228765b0e115b0534ca76d10c949afcb4bd50cdd.tar.bz2
added notes about weakref changes
Diffstat (limited to 'Misc')
-rw-r--r--Misc/NEWS15
1 files changed, 15 insertions, 0 deletions
diff --git a/Misc/NEWS b/Misc/NEWS
index 9d2e354..f7f6ffb 100644
--- 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.