Mark Dickinson added the comment:

Applied.  Thanks!

I'm not sure whether this is worthy of inclusion in Python 3.3.0;  on one hand, 
it's a segfault from core Python.  On the other, it doesn't look that easy to 
trigger by accident.

On balance, I'd say it's safe to wait for Python 3.3.1 for this.  Adding Georg 
to the nosy in case he disagrees.

----------
nosy: +georg.brandl

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue16060>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to