#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 Tim Graham):
I agree anything user-facing should be an exception, but it might not be
necessary to replace all usages. For example, there might be `assert`
conditions in the ORM that aren't expected to be triggered unless there's
some bug in Django. In this case, the `assert` merely helps when
refactoring, etc.
--
Ticket URL: <https://code.djangoproject.com/ticket/32508#comment:3>
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.b61a964a677b4d9b64e286fc2c6ac2cb%40djangoproject.com.
