Georg Brandl added the comment:
Out of date now that 2.7 is also in maintenance mode.
--
nosy: +georg.brandl
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5970
Antoine Pitrou pit...@free.fr added the comment:
Adding some tests to check that a bug is /not/ fixed looks weird to me.
If we did that for every trunk change that we don't want to end up in
the stable branch, there'd be lots of new tests of dubious utility.
Besides, py3k isn't affected ;)
Barry A. Warsaw ba...@python.org added the comment:
I agree with Antoine.
--
versions: -Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5970
___
Jeffrey Yasskin jyass...@gmail.com added the comment:
Re py3k: oops, thanks for checking.
Re 2.6: Fine with me, second patch removed.
--
assignee: barry -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5970
Changes by Jeffrey Yasskin jyass...@gmail.com:
Removed file: http://bugs.python.org/file13928/exc_info_26.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5970
___
New submission from Jeffrey Yasskin jyass...@gmail.com:
There's an obscure bug in sys.exc_info after a yield statement.
def test():
def raising_generator():
try:
raise IndexError(inner exception)
except IndexError:
yield 3
#
Jeffrey Yasskin jyass...@gmail.com added the comment:
I think we should _not_ backport any fix for this bug to the 2.6 series,
since any changes to user behavior would be pretty subtle. To prevent
that backport, I'd like to apply exc_info_26.patch to the 2.6 branch,
with Barry's approval.
