#32508: Raise proper exceptions instead of using "assert".
--------------------------------------+------------------------------------
Reporter: Adam Johnson | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Carlton Gibson):
> If a system check is a good idea on DRF...
Yeah... **if** — note I said **maybe** (with emphasis). I'm kind of -0 on
this (for here or there) — I don't think we can sustainably add system
checks for every which way you might possibly shoot yourself in the foot.
If using `-O` is a bad move, that's something that Python should warn
about no?
I don't know that the issue tracker is the best place to knock this back
and forth. The first four responses here seem against adding a system
check, without at least doing various other things first, so I think we're
a way from a consensus **to add** one…
--
Ticket URL: <https://code.djangoproject.com/ticket/32508#comment:13>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.3938879676860519692cde0d6272ac5b%40djangoproject.com.
