Can't you copy whatever data you want from the request into the session data (request.session.<whatever> = request.<whatever>) in a view, middleware, or wherever? That seems like the proper separation of concerns.
On Wednesday, April 15, 2020 at 11:50:13 AM UTC-4, Lorenzo Peña wrote: > > Now, in order to follow the path suggested in the Django documentation for > overriding database backed sessions, some of the data one might need to > store in the session model is coming from the request, and Django is not > passing the request when instantiating the session store. > > Do you think there is a point in requesting that the request object (if > available) is passed as an optional parameter when creating the session? > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d9eef373-28cf-4ccb-9801-90d7c38b3678%40googlegroups.com.
