don't use crash_handler by default #1008

merged 3 commits into from Nov 20, 2011

2 participants

IPython member

Now the excepthook shows a regular traceback, with a brief message about reporting bugs and how to enable to the big crash handler. Adding a more/0 to interact inside if more:, I get:

In [1]: if 1:
Traceback (most recent call last):
  File "/prefix/bin/ipython", line 9, in <module>
    load_entry_point('', 'console_scripts', 'ipython')()
  File "/prefix/IPython/frontend/terminal/", line 393, in launch_new_instance
  File "/prefix/IPython/frontend/terminal/", line 367, in start
  File "/prefix/IPython/frontend/terminal/", line 220, in mainloop
  File "/prefix/IPython/frontend/terminal/", line 288, in interact
ZeroDivisionError: integer division or modulo by zero

If you suspect this is an IPython bug, please report it at:
or send an email to the mailing list at

You can enable a much more verbose crash handler with:
    %config Application.verbose_crash=True

small fixes along the way:

  • current Application added to configurables list, for use in %config.
  • email addresses in full crash reports changed to ipython-dev, so they don't go straight to individual users.

Should close #695, and ameliorate #833 (doesn't fix the bug, but the message is more sensible)

minrk added some commits Nov 17, 2011
@minrk minrk include parent Application in InteractiveShell.configurables
for use in %config magic
@minrk minrk use ipython-dev as the email address for crash reports a6e5b20
@minrk minrk Don't use crash_handler by default
adds crash_handler_lite for adding a short message after a regular

Application.verbose_crash configurable determines which to use
IPython member

Great! Code looks clean, tested it. Nice to get rid of those endless crash reports... Merging now.

@fperez fperez merged commit 493f6d4 into ipython:master Nov 20, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment