Changes by Larry Hastings la...@hastings.org:
--
nosy: +larry
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14241
___
___
Python-bugs-list mailing
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14241
___
___
Python-bugs-list mailing
Mark Shannon m...@hotpy.org added the comment:
io.UnsupportedOperation.__new__(io.UnsupportedOperation)
behaves correctly now (rev d9c98730e2e8)
This bug was (I believe) caused somehow by an error in OSError_new() which did
not initialize self-args if OSError_init() was not called.
Here is a
Changes by Benjamin Peterson benja...@python.org:
--
resolution: fixed - out of date
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14241
___
___
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14241
___
___
Python-bugs-list mailing
New submission from Mark Shannon m...@hotpy.org:
io.UnsupportedOperation.__new__(io.UnsupportedOperation)
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: ValueError.__new__(UnsupportedOperation) is not safe, use
OSError.__new__()
Looking at the mro of
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14241
___
___
Python-bugs-list
Changes by Terry J. Reedy tjre...@udel.edu:
--
stage: - patch review
versions: +Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14241
___
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14241
___
___
Python-bugs-list
