On 5/18/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > I'm +1 on these changes, including using "!" as the "look somewhere > else for the password" designator.
Would it really be "look somewhere else for the password" or would it be more like "if you got this far (all other authentication methods failed), and you got this value (no password is stored), you're out of luck"? It may seem like a strange distinction to make, but it goes a bit to the philosophy of it, which could affect its implementation in general. The way you worded it, I would expect the implementation to check try a password first, and if it doesn't find one, it would then look at other sources (like OpenID). This would mean that users would be required to not have a password in order for other schemes to work. I doubt that's the way you meant it, but it might be worth being clear on the subject, especially if the process gets documented for the sake of future authentication authors. I'm probably just splitting hairs though, so disregard as necessary. -Marty --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---