Tim, They aren't really silenced, but skipped. I would like to silence them for real. They are skipped, but still printed out.
Let's assume that I am a guy who wants to silence every system check. 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) * messages are still visible (I don't need them and I don't want to read them, and any other developer don't want to read them) * django bootstraping is still slower due to executing system checks. As an old-and-experienced-guy I want to disable (completely) system checks on my responsibility. Just belive me - I know what I'm doing. And I don't want to hack Django to do any non-typical things. Why you can't add just one setting to bypass something which is currently built-in? Is that a really big problem? On Friday, August 7, 2015 at 2:32:08 PM UTC+2, Tim Graham wrote: > > Could you elaborate on why disabling system checks entirely is better than > selectively disabling checks that are problematic for you? Is it really > never helpful? If there are more people clamoring for this feature, I think > I'd be more open to it. > > SILENCED_SYSTEM_CHECKS = ['admin.E108', 'admin.E304', 'fields.E305', > 'admin.E116', 'fields.E306', 'fields.W342', 'fields'W340'] > > On Friday, August 7, 2015 at 4:35:37 AM UTC-4, Marcin Nowak wrote: >> >> >> >> On Thursday, August 6, 2015 at 5:36:09 PM UTC+2, Tim Graham wrote: >>> >>> Perhaps your monkeypatches should be moved to `AppConfig.ready()` >>> methods so they are applied before the system check framework is invoked? >>> >> >> I'll try that, thanks. To be honest I should remove monkeypatching, I >> don't like it, but I don't want do it now. >> >> >>> >>> >> How many problematic checks are you running into? >>> >> >> Above 60 overall. >> >> Can you describe them a bit more? If anything, SILENCED_SYSTEM_CHECKS = >>> ['*'] to disable checks seems like the best option that Josh proposed, but >>> I'd like more justification before we spend time doing that. >>> >> >> E108, E304, E305, E116, E306, many W342, W340. >> I'm using many mappings for read-only and they don't need to be valid as >> regular models. >> >> Cheers, >> Marcin >> > -- 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/558031ee-4ebd-4e39-89c6-4ddf84b0ea04%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
