[issue4047] test_run_abort triggers CrashReporter on MacOS X

Ronald Oussoren added the comment: Backported to 3.1 in r83069, 2.7 in r83079, 2.6 in r83083 -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue4047] test_run_abort triggers CrashReporter on MacOS X

Ronald Oussoren added the comment: Committed a fix in r83067 (py3k), will backport to other active branches shortly. -- versions: -Python 3.2 ___ Python tracker ___ ___

[issue4047] test_run_abort triggers CrashReporter on MacOS X

Martina Oefelein added the comment: Yes, a warning at the start of the test would at least let the user know that the crash is expected. -- ___ Python tracker ___ __

[issue4047] test_run_abort triggers CrashReporter on MacOS X

Ronald Oussoren added the comment: Triggering the crash reporter is unavoidable. What we could do is print a warning that this will happen at the start of the test. -- ___ Python tracker _

[issue4047] test_run_abort triggers CrashReporter on MacOS X

Changes by Ned Deily : -- assignee: -> ronaldoussoren components: +Macintosh nosy: +ronaldoussoren versions: +Python 3.2 -Python 3.0 ___ Python tracker ___ __

[issue4047] test_run_abort triggers CrashReporter on MacOS X

Martina Oefelein added the comment: Retested in Python 2.6.5, 2.7, 3.0.1, 3.1.2: same result -- versions: +Python 2.6, Python 2.7, Python 3.1 ___ Python tracker ___ _

[issue4047] test_run_abort triggers CrashReporter on MacOS X

New submission from Martina Oefelein <[EMAIL PROTECTED]>: test_run_abort (in test_subprocess.py) causes the MaxOS X crash reporter dialog to pop up (at least when running from an interactive session). This might be unavoidable (the crash is part of the test); however, to avoid confusion, it sh