Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
228765b0
Commit
228765b0
authored
Feb 06, 2004
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
added notes about weakref changes
parent
d310f13c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
0 deletions
+15
-0
Misc/NEWS
Misc/NEWS
+15
-0
No files found.
Misc/NEWS
View file @
228765b0
...
...
@@ -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.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment