You're quite welcome. One other thing I forgot to mention: nosetest.py has a --with-coverage option, and Django support. I've used it to coverage test my Django code.
--Ned. Marcin Kaszynski wrote: > > On Nov 25, 3:58 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> > wrote: > >> We recently added the >> ability for external projects to define new management commands >> specifically so that end-users could contribute features like this >> without the need to modify the Django core. >> > > I did not know that. Very cool. > > >> And, to pre-empt the follow on discussion - this policy of including >> other libraries is not up for debate. You may disagree, but we're not >> going to change it. >> > > Nope, after reading your explanation I think that is a good policy, > especially if there is a way to do such things via external add-ons. > > But we do have Ned's direct permission and the file does include > licensing information that basically means you can redistribute it in > source form as long as you don't remove the comments. So, we're back > to "think about the best way to handle the option", right? :) > > Ned: thanks for your work on the module, it is incredibly helpful > during testing. I spent the last two days adding tests and removing > unused code from my apps. > > -mk > > > > > -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
