#27301: Better handling of errors that are not pickleable when testing in 
parallel
-------------------------------------+-------------------------------------
     Reporter:  Adam Wróbel          |                    Owner:  (none)
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Testing framework    |                  Version:  1.10
     Severity:  Normal               |               Resolution:
     Keywords:  testrunner parallel  |             Triage Stage:  Accepted
  pickle                             |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Chris Jerdonek):

 Thanks. Re: botocore, it would seem reasonable to me for them to accept a
 PR that fixes it only for 3.x and/or future versions of botocore if fixing
 it for 2.x is too difficult and/or would break backwards compatibility.

 Also, on a related note, if it turns out that picklability of exceptions
 is too much to expect in general, then I think we should consider not
 having Django's test runner   error out if the exception isn't picklable.
 But that can be handled in the "part 2" ticket when that is created.

--
Ticket URL: <https://code.djangoproject.com/ticket/27301#comment:9>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.dfe62254ab058fc0b8dcce181b412069%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to