#32114: Workaround for subtest issue with parallel test runner
-------------------------------------+-------------------------------------
Reporter: Jordan Ephron | Owner: Jordan
Type: | Ephron
Cleanup/optimization | Status: assigned
Component: Testing framework | Version: 3.1
Severity: Normal | Resolution:
Keywords: Test subtest | Triage Stage: Accepted
parallel |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chris Jerdonek):
I took a look at the proposed PR for this issue. I want to mention that
there's another approach to the whole "pickleability" issue. The problem
with the pickling approach is that I don't think it can ever be completely
solved. It seems like there will always be cases that can't be pickled, so
attempts at further fixing will always be partial workarounds.
Another approach is to render the exception to a string when the exception
first happens, and to pass the string back (as strings ''are''
pickleable). This approach is discussed further in #29023, and a proof-of-
concept patch is linked to there. Another advantage of first rendering to
a string is that the full exception chain gets captured, which I don't
think pickling addresses either (last I checked). (Ticket #29023 is about
the exception chain aspect.)
--
Ticket URL: <https://code.djangoproject.com/ticket/32114#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.589a4ddc6cdca4b8655c9308e236a5ac%40djangoproject.com.
