Ticket opened for documentation: https://code.djangoproject.com/ticket/17236
On Nov 15, 3:35 pm, Byron Ruth <bjr...@gmail.com> wrote: > Indeed, all of the settings are slowly becoming unwieldy. I will write > my own `login()` function in the meantime, but the docs should > definitely be update to note this behavior. > > On Nov 15, 2:27 pm, ptone <pres...@ptone.com> wrote: > > > > > > > > > On Nov 15, 10:44 am, Byron Ruth <bjr...@gmail.com> wrote: > > > > How would everyone feel about making this a setting, e.g. > > > SESSION_FLUSH_AT_LOGIN? If false, it would behave as it does now > > > otherwise it would flush the non-auth session. > > > I do think the current behavior is worth a note in the docs - like you > > say - there are reasons to not flush it. > > > but this doesn't seem to merit a setting in the face of the ever > > growing problem of settings bloat. > > > Ifhttps://code.djangoproject.com/ticket/17209comesto pass, this > > could be something on a login class, but otherwise I think you are > > better off just doing a custom login view if you want to flush the > > session. > > > -Preston -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
