#34482: Unable to access "non-picklable" attributes of empty HttpRequest and
HttpResponse objects after shallow copy.
---------------------------------+-----------------------------------------
     Reporter:  Anvesh Mishra    |                    Owner:  Anvesh Mishra
         Type:  Bug              |                   Status:  assigned
    Component:  HTTP handling    |                  Version:  4.2
     Severity:  Release blocker  |               Resolution:
     Keywords:                   |             Triage Stage:  Accepted
    Has patch:  0                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  1                |                    UI/UX:  0
---------------------------------+-----------------------------------------

Comment (by Anvesh Mishra):

 Created the required [https://github.com/django/django/pull/16753 PR]. I
 don't know if this patch will work as Adam pointed out various
 possibilities that can occur in his
 [https://code.djangoproject.com/ticket/34484 comments on this ticket].
 Didn't add the regression tests yet due to the regressions added in
 d7f5bfd241666c0a76e90208da1e9ef81aec44db and
 6220c445c40a6a7f4d442de8bde2628346153963. Maybe we could add regressions
 for `WSGIRequest` and `ASGIRequest` as pointed out by
 [https://code.djangoproject.com/ticket/34484#comment:2 Adam Jhonson in
 this comment].

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34482#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/010701877216f61d-9fd17642-68b9-42ed-81f5-15914e8e5075-000000%40eu-central-1.amazonses.com.

Reply via email to