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
017fbf31
Commit
017fbf31
authored
Jan 10, 2006
by
Georg Brandl
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Remove outstanding_crashes again.
parent
d8b58872
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
38 deletions
+0
-38
Lib/test/outstanding_crashes.py
Lib/test/outstanding_crashes.py
+0
-38
No files found.
Lib/test/outstanding_crashes.py
deleted
100644 → 0
View file @
d8b58872
#
# This file is for everybody to add tests for crashes that aren't
# fixed yet. Please add a test case and appropriate description.
#
# When you fix one of the crashes, please move the test to the correct
# test_ module.
#
import
unittest
from
test
import
test_support
# Bug 1377858
#
# mwh's description:
# The problem is obvious if you read typeobject.c around line 660: the weakref
# list is cleared before __del__ is called, so any weakrefs added during the
# execution of __del__ are never informed of the object's death.
import
weakref
ref
=
None
class
TestBug1377858
(
unittest
.
TestCase
):
class
Target
(
object
):
def
__del__
(
self
):
global
ref
ref
=
weakref
.
ref
(
self
)
def
testBug1377858
(
self
):
w
=
self
.
__class__
.
Target
()
w
=
None
print
ref
()
def
test_main
():
test_support
.
run_unittest
(
TestBug1377858
)
if
__name__
==
"__main__"
:
test_main
()
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