#28790: Provide a mixin to run certain test classes not in parallel
-----------------------------------+--------------------------------------
Reporter: Tobias Krönke | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by Tobias Krönke):
I don't want to be too eager for this to be merged. I probably wouldn't
have looked any further had I known this Mixin. Still I would like to
point out some advantages of my solution:
- Less complex to use
- Less complex implementation (especially no lock files involved)
- More efficient, if you have only 1 shared resource (no concurrent waits
for the locked file)
Of course I also see the advantage of the existing mixin, that you can use
different lock files for different shared resources if you have many. A
hint in the docs would be quite pleasant.
So, your call ;-)
--
Ticket URL: <https://code.djangoproject.com/ticket/28790#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 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/062.8697442cf9b878f6424e05690deb6c76%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
