#16563: Error pickling request.user
----------------------------------------+------------------------------
Reporter: zero.fuxor@… | Owner: nobody
Type: Bug | Status: closed
Milestone: | Component: contrib.auth
Version: 1.3 | Severity: Normal
Resolution: wontfix | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------+------------------------------
Changes (by PaulM):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
Some things aren't pickleable. It's a known limitation at the Python
level, and is unlikely to change. Is Django itself trying to do this
somewhere? Is there an extremely good reason this should be possible? I'm
closing this as wontfix. Please feel free to reply if you've got good
answers to these questions.
--
Ticket URL: <https://code.djangoproject.com/ticket/16563#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 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-updates?hl=en.
