#33331: Improve exception handling with `cursor.close()` after errors -------------------------------------+------------------------------------- Reporter: Daniel Hahler | Owner: nobody Type: | Status: closed Cleanup/optimization | Component: Database layer | Version: 3.2 (models, ORM) | Severity: Normal | Resolution: wontfix 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 Daniel Hahler): The main issue here is not about how to raise in case it should be raised, but to not raise in the first place, if an error is expected. It is meant to fix https://code.djangoproject.com/ticket/16614#comment:31 again, which regressed. -- Ticket URL: <https://code.djangoproject.com/ticket/33331#comment:5> 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/065.389a4cd0d683b53ba76d3a476d878909%40djangoproject.com.