As I said some time ago - there should be a possibility to disable system
checks (generally), and run them only when needed (i.e. by adding
--system-check argument to mgmt command(s)).
Kind Regards,
Marcin
On Tuesday, October 20, 2015 at 12:02:31 PM UTC+2, Shai Berger wrote:
>
> Just brainstorming : by all of the above, it would seem that the best
> default is to run checks unless specific tests are selected. Of course,
> this could be perceived as inconsistent, and that would be a problem.
>
> On 20 באוקטובר 2015 10:04:17 GMT+03:00, Aymeric Augustin <
> aymeric....@polytechnique.org <javascript:>> wrote:
>>
>> 2015-10-20 2:48 GMT+02:00 Tim Graham <timog...@gmail.com <javascript:>>:
>>
>>> me: I'm of the opinion that running the system checks as part of the
>>> manage.py
>>> test command should be opt-in (for example, by writing a test that
>>> asserts the call_command('check') output is empty. For example, when
>>> debugging a single test, it doesn't seem necessary to have the overhead of
>>> running check.
>>>
>> I share this opinion. Single-test run time is a very important use case,
>> not only for TDD practitioners, but also for everyone who tries to fix a
>> stubborn failing test.
>>
>>
>>
>> --
>> Aymeric.
>>
>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
--
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/4abd21c6-5499-4a68-9ea6-2a662d622409%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
