Hi all,
On Tuesday 11 August 2015 19:05:26 Carl Meyer wrote:
> On 08/11/2015 10:44 AM, Marcin Nowak wrote:
> > I need to list ALL errors and warnings, which is:
> > * unhandy and it would require maintain a big list (especially after
> > upgrading Django to newer version)
>
> That's a good reason not to include this "feature." How can you say now
> that a check included in a future Django version won't be relevant to
> you or catch a bug in your code, when you don't even know yet what that
> check is?
>
Further -- the cheks framework allows your apps or 3rd-party apps to add
checks of their own. So, the above argument also multiplies to all future
versions of all apps you use.
>
> All that said, [...] I think users who don't understand how
> SILENCED_SYSTEM_CHECKS works may be tempted to use it to "just make the
> errors go away", but all in all I'm still only -0.5.
>
FWIW, I'm -1.
I could be supportive of a --without-system-checks flag, which I can see useful
during development ("I know there's a problem here, I want to solve something
else first"). This would imply that a user needs to decide, every run anew,
that they don't want the checks. I'm aware that a user like Marcin could just
use an alias, or change their manage.py, to have the flag included
automatically; I'd take a "consenting adults" approach towards that sort of
abuse.
Shai.
