#34327: Test client session does not work as described when using signed cookie
engine
-------------------------------------+-------------------------------------
Reporter: Sergei | Owner: nobody
Type: Bug | Status: closed
Component: Testing framework | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: session | Triage Stage:
signed_cookies | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
Hi Sergei.
I'm going to mark this as `wontfix`, as I'm not sure it's worth even the
clarification Mariusz offered. (For me, it clearly reads as assume the
default backend — it's an example...) If you want to make that tweak, I
don't object though.
> ...could be handled internally in the ClientMixin, independent of a
concrete store implementation (it already does everything actually).
I don't see from what's written here exactly what you have in mind. If you
wanted to make a draft PR showing the API changes then we could see if it
looks worthwhile.
(If folks think so, then we can reopen here.)
I hope that makes sense. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/34327#comment:4>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070186593c900f-4f5e32d3-8991-49de-9b13-5920f367b7bf-000000%40eu-central-1.amazonses.com.
