#30249: Deprecate re-raising view exceptions from test client in tests
     Reporter:  Jon Dufresne         |                    Owner:  nobody
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Testing framework    |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0

Comment (by Carlton Gibson):

 Hey Jon.

 Thanks for the follow-up.

 Quick comments:

 1. Some helper would be better yes. `assertResponseException()` or such.
 2. The issue with the setting isn't that you invented it or not: rather
 it's using a setting, which has other purposes, to control the test-client

 I like and use the current behaviour. Maybe one-day we remove
 `DEBUG_PROPOGATE_EXCEPTION`, for a custom `handler` subclass or such. What
 do I do then? (For me 🙂) clearly the right answer is a flag on
 `TestClient`, which we already have.

 (**Maybe** then swapping the default...? — but ''meh''... grrrr...)

 (Re, the churn, yes, if we think it's an improvement then the churn is
 worth it — I'm just not there as yet.)

Ticket URL: <https://code.djangoproject.com/ticket/30249#comment:4>
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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to