Chris Ryland wrote:
Couldn't you just define your own functions as you've done, but invoke the django.contrib.auth.view.login/logout functions directly before your pre-/post-processing?
Yeah, I thought about that not long after my original post. ;-) It works, and as long as the method signatures/defaults don't change in django.contrib.auth.view.login/logout, it should be okay. If my login/logout functions were to break in the future, it shouldn't be too difficult to figure out why. Jeff Bauer --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
