#10378: authenticate() method should not continue on built-in or generic
exceptions
---------------------------------------------+------------------------------
Reporter: bendavis78 | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: 1.0
Resolution: | Keywords: authenticate
TypeError
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by mtredinnick):
Would be backwards incompatible. I know we've said "contrib" has an
exception from the backwards compatibility guarantee, but we still
shouldn't make changes like this without strong reason, particularly in
something as heavily used as the authentication area. We fail safe here
(don't let anybody in if things are raised), so it's only a
diagnostic/debugging issue, not a functionality one.
I'm pretty close to -1 on making this change at the moment. It's
unfortunate, but not that harmful to leave it as is.
--
Ticket URL: <http://code.djangoproject.com/ticket/10378#comment:2>
Django <http://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
-~----------~----~----~----~------~----~------~--~---
