On Tue, Jan 19, 2010 at 12:39 AM, Eric Holscher <eric.holsc...@gmail.com> wrote: > Saw this go in, and it gets a huge +1 from me as well. However, I know that > in the past we have talked about adding other things to the test runner > (like coverage, etc), so it would seem like now would be a good time to > recommend accepting **kwargs in your custom test runners, so that when we > add in more abilities in the future, we don't blow up people's old test > runners that they have that don't support new options.
True - thats worth a note in the docs. I've made the change in r12259. Yours, Russ Magee %-)
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
