                                                                                                                                                                                                                                                                
Received-SPF: pass (google.com: domain of dcra...@gmail.com designates 209.85.212.181 as permitted sender) client-ip=209.85.212.181;
References: <e307a4c3-f8de-4158-9e59-e24c6da8ae37@googlegroups.com>
In-Reply-To: <e307a4c3-f8de-4158-9e59-e24c6da8ae37@googlegroups.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <EA2C77E3-E465-4D57-AA44-AAEF96B89...@gmail.com>
Cc: "getsentry@googlegroups.com" <getsentry@googlegroups.com>
From: David Cramer <dcra...@gmail.com>
Subject: Re: Raven automatically reports uncaught exceptions
Date: Sun, 8 Jul 2012 12:34:01 +0200
To: "getsentry@googlegroups.com" <getsentry@googlegroups.com>

It's the default behavior of Raven. Currently there's no easy way to disable=
 it

On Jul 8, 2012, at 4:43 AM, Taras D <taras...@gmail.com> wrote:

> Hi group,
>=20
> Just a quick question. I've noticed that no matter what i do in terms of l=
ogging configuration, that if I have the raven.contrib.django app installed,=
 then errors will go to sentry. It's not a massive problem apart from affect=
ing my setup to ensure that I don't log things twice, just wondering what is=
 causing this behaviour.
>=20
> Thanks
>=20
> Taras