On Mon, Jan 12, 2009 at 18:04, mrts <mrts.py...@gmail.com> wrote: > As of now, I'll stop pursuing this further, but when I come back to > this, > would the approach outlined in http://dpaste.com/108140/ be > acceptable? > > I.e. if > 1) not specified explicitly (by the --multiprocessing option to test) > 2) there's only a single core in the system > 3) importing the multiprocessing module fails > run the ordinary single-process test runner.
Django doesn't need this yet but to show what is happening elsewhere... CPAN have plans for fully automated testing: an os-image with the needed libraries is created and distributed, tests are run in the vhost and results are sent to an accumulator, in essence: c...@home... :) HM --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
