#27035: DiscoverRunner's setup_test_environment() hard-codes settings.DEBUG to
False
--------------------------------------+--------------------
Reporter: cjerdonek | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
Currently, the `setup_test_environment()` method of Django's
`DiscoverRunner` hard-codes setting `settings.DEBUG` to False. See
[https://github.com/django/django/blob/a6baada7bdf0c2b14045ee86364f9401c7b91b7c/django/test/runner.py#L414
here] for a direct link to that code.
This is less convenient for subclassers that would like to provide the
ability to selectively run certain tests with `DEBUG` set to True (e.g.
see [https://code.djangoproject.com/ticket/27008 here] for a ticket to
expose this as a command-line option).
This ticket is to make subclassing easier by adding a `debug_mode`
instance attribute to `DiscoverRunner` (the suffix "mode" is to better
distinguish from the current `debug_sql` attribute). This would also make
progress towards ticket #27008.
--
Ticket URL: <https://code.djangoproject.com/ticket/27035>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.c0db3ab4e541ab2bde08c40a3281dc5d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
