New submission from Richard Oudkerk shibt...@gmail.com:
If you subclass OSError without calling OSError.__init__() then you can get a
crash. For example
Python 3.3.0b1 (default:cfbe51e66749, Jun 30 2012, 20:50:54) [MSC v.1600 32
bit
(Intel)] on win32
Type help, copyright, credits or
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +pitrou
priority: normal - high
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15229
___
___
Antoine Pitrou pit...@free.fr added the comment:
Here is a quick patch (needs a test):
diff --git a/Objects/exceptions.c b/Objects/exceptions.c
--- a/Objects/exceptions.c
+++ b/Objects/exceptions.c
@@ -834,6 +834,7 @@ oserror_init(PyOSErrorObject *self, PyOb
#endif
/* Steals the
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 1cbab581bf1e by Antoine Pitrou in branch 'default':
Issue #15229: An OSError subclass whose __init__ doesn't call back
http://hg.python.org/cpython/rev/1cbab581bf1e
--
nosy: +python-dev
Antoine Pitrou pit...@free.fr added the comment:
It should be fixed now.
--
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15229
