On 08/25/2015 08:57 AM, Marcin Nowak wrote: > Well, I'm not sure now, because Tim wrote that it was a design decision > and it is well documented.
I still think we should change that design. It is simply wrong to have a setting called `SILENCED_SYSTEM_CHECKS` that fails to actually _silence_ the check IDs listed. > Also please note that silencing specific errors is not the best solution. > In the first case E116 may be untrue and may be silenced, but for other > models this error may be true and shouldn't be silenced at all. > Silencing all E116 will give us messy information about state. That's why I think in this case the best solution is to actually fix the error, not silence it; Django should be able to find a find a field even if it's monkeypatched-in, as long as the monkeypatch happens in time. Carl -- 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/55DC83A8.8050907%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
