don't use crash_handler by default #1008

minrk · 2011-11-17T21:42:54Z

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('ipython==0.12.dev', 'console_scripts', 'ipython')()
  File "/prefix/IPython/frontend/terminal/ipapp.py", line 393, in launch_new_instance
    app.start()
  File "/prefix/IPython/frontend/terminal/ipapp.py", line 367, in start
    self.shell.mainloop()
  File "/prefix/IPython/frontend/terminal/interactiveshell.py", line 220, in mainloop
    self.interact(display_banner=display_banner)
  File "/prefix/IPython/frontend/terminal/interactiveshell.py", line 288, in interact
    more/0
ZeroDivisionError: integer division or modulo by zero

If you suspect this is an IPython bug, please report it at:
    https://github.com/ipython/ipython/issues
or send an email to the mailing list at ipython-dev@scipy.org

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)

for use in %config magic

adds crash_handler_lite for adding a short message after a regular traceback. Application.verbose_crash configurable determines which to use

fperez · 2011-11-20T10:34:00Z

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

Use a much more restrained crash handler by default. Now the excepthook shows a regular traceback, with a brief message about reporting bugs and how to enable to the big crash handler. Our previous, extremely verbose crash handler can still be activated via `%config Application.verbose_crash=True`, so we can debug real crashes or ask users for extra detail easily. 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).

Use a much more restrained crash handler by default. Now the excepthook shows a regular traceback, with a brief message about reporting bugs and how to enable to the big crash handler. Our previous, extremely verbose crash handler can still be activated via `%config Application.verbose_crash=True`, so we can debug real crashes or ask users for extra detail easily. 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 ipython#695, and ameliorate ipython#833 (doesn't fix the bug, but the message is more sensible).

minrk added 3 commits November 17, 2011 13:54

include parent Application in InteractiveShell.configurables

69c13a1

for use in %config magic

use ipython-dev as the email address for crash reports

a6e5b20

Don't use crash_handler by default

bb6f87b

adds crash_handler_lite for adding a short message after a regular traceback. Application.verbose_crash configurable determines which to use

fperez merged commit 493f6d4 into ipython:master Nov 20, 2011

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

don't use crash_handler by default #1008

don't use crash_handler by default #1008

minrk commented Nov 17, 2011

fperez commented Nov 20, 2011

don't use crash_handler by default #1008

don't use crash_handler by default #1008

Conversation

minrk commented Nov 17, 2011

fperez commented Nov 20, 2011