Django logs shell exceptions (with Django > 2.0)

I’m not completely sure whether this is a change in Django or in Raven.

I’ve started seeing typos in the manage.py shell log to Sentry since I upgraded to django 2.0, raven 6.4.0 and Python 3.6. I’ve come up with a hacky work around, but it did clarify that there’s no easy way to disable the sentry client that I could find documented.

Is there any change at this end which might have caused this?

[jacobwegner]

I think I’ve tracked this down to the (good!) change that happened between 6.0.0 and 6.1.0:

fix registration of hooks for Django

PR: https://github.com/getsentry/raven-python/pull/966

Original issue: https://github.com/getsentry/raven-python/issues/884

Since install_sys_hook is working correctly, exceptions raised within a manage.py|django-admin.py session are handled by Sentry.

Here is a basic workaround I’ve settled on (YMMV):

# in settings.py
import sys
SHELL = "shell" in sys.argv
...
RAVEN_CONFIG = {
    "ignore_exceptions": ("*") if SHELL else ()
}

In should_capture, the wildcard"*" will match any exception.

Other manage.py commands that don’t have a “shell” argument will continue to send exceptions to Sentry.

[rowanseymour]

@jacobwegner it still works (thanks!), but I think in your solution you meant ("*",) instead of ("*")?