#36819: Async login does not reuse authenticated user instance
-------------------------------------+-------------------------------------
Reporter: Mykhailo Havelia | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: contrib.auth | Version: 6.0
Severity: Normal | Resolution: wontfix
Keywords: async auser alogin | Triage Stage:
cache | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* keywords: async => async auser alogin cache
* resolution: => wontfix
* status: new => closed
Comment:
Hello Mykhailo Havelia, thank you for your ticket and for linking to the
PR conversation.
I gotta say, as soon as I read this ticket description, my first gut
reaction was twofold:
1. why a project would mix async and sync in the same flow, and
2. a shared cache feels like the perfect recipe for a debugging nightmare
Reading Mariusz and Carlton's comment in the PR, seems like we are in
agreement. Closing following that rationale, if you feel strongly that
this caching is key for a given use case, please share specific details in
how a single request would benefit from it.
--
Ticket URL: <https://code.djangoproject.com/ticket/36819#comment:1>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019b4c5c28de-c8d64d39-db62-4802-b8d6-a3f055cc57ca-000000%40eu-central-1.amazonses.com.
