Tim Peters <t...@python.org> added the comment: Segfaults are different: they usually expose an error in CPython's implementation. We don't prioritize them because the user may have to restart their program (who cares? <0.5 wink>), but because they demonstrate the language implementation is accessing memory wildly. That in turn can result in anything, from arbitrarily wrong program results, through file corruption, to massive security holes. It's far more a "correctness" than a "usability" concern.
If a user provokes a segfault by (ab)using low-level facilities (say, ctypes), we don't care - that's on them. But most segfaults have pointed to legitimate corner-case errors in CPython itself. There's no correctness issue in whether iterators are always interruptible - it doesn't merit the same concern. ---------- nosy: +tim.peters _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31815> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
