#15901: Django should wrap all PEP 249 exceptions in db.utils
-------------------------------------+-------------------------------------
Reporter: xiaket | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by gcbirzan):
It turns out that this behaviour was introduced in a fix by Antoine Pitrou
(http://hg.python.org/cpython/rev/d6e86a96f9b3/#l8.10). The same patch
didn't make it into 2.x, and that branch got a fix that didn't break ABC
(http://hg.python.org/cpython/rev/7e86fa255fc2), which was later refined
(http://hg.python.org/cpython/rev/57de1ad15c54) to account for insane
recursion limits. I'll take it up on python-dev tomorrow, to see if
applying the 2.x fix would be a good idea for 3.x, so I think this should
be put on hold until then.
Of course, there's the alternative of patching the bases for Python 3, but
I still think that's just... weird.
--
Ticket URL: <https://code.djangoproject.com/ticket/15901#comment:20>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
