10 | | 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. (Even if we don't remove it, using the setting this way is—to use the official technical term—horrific 🙂) |
| 10 | 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. |
| 11 | |
| 12 | (Even if we don't remove it, using the setting this way is—to use the official technical term—horrific 🙂: a flag on `TestCient` is just right, and I'm very glad you added it, after all these years.) |