Marcin - you can "tidy up" some monkey patches, or at least make them
robust to the code you're replacing changing, by
using https://github.com/adamchainz/patchy .
I'm -1 - we've recently been implementing project system checks for our
team and they are super useful. We even have one that checks if
requirements.txt has been updated since the virtual environment was
created. It would be bothersome if there was a way for developers to
disable *all* checks for themselves. Also whilst many 3rd-party apps are
adding checks recently, you don't want to miss out on the help they provide.
On Wednesday, August 12, 2015 at 6:35:34 PM UTC+1, Shai Berger wrote:
>
> 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.
>
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/fa7b4deb-b373-4363-8264-9288ba15085a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
