I don't see a fix any time soon in DCMS's future, but this can't be the
only library with a similar issue.
It would be good if I could mark a test as @parallel_unsafe so that the
rest of the tests could run in parallel, while all the parallel_unsafe
tests would be guaranteed to run one at a time.
--
Ticket URL: <https://code.djangoproject.com/ticket/31168>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* version: 3.0 => master
* resolution: => wontfix
Comment:
You can [https://docs.djangoproject.com/en/3.0/topics/testing/advanced
/#enforce-running-test-classes-sequentially Enforce running test classes
sequentially]. I don't think that marking a single test as "parallel
unsafe" is necessary and doable.
--
Ticket URL: <https://code.djangoproject.com/ticket/31168#comment:1>