#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 Adam Johnson): > I don't think we can sustainably add system checks for every which way you might possibly shoot yourself in the foot. True - I just get tired of repairing feet 😅 > I don't know that the issue tracker is the best place to knock this back and forth. Agree. Let's just stick with the current proposal to remove use of assert in prod code. I made an issue for DRF: https://github.com/encode/django- rest-framework/issues/7831 -- Ticket URL: <https://code.djangoproject.com/ticket/32508#comment:15> 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/068.f3aa3f54b58ffe1a54a2777819a3fbf0%40djangoproject.com.