Please use coverage.py, I would be honored to have it included in Django 
core.  If it's better as an add-on of some sort, that's great too.  Let 
a thousand flowers bloom!

--Ned.

Todd O'Bryan wrote:
> On Nov 24, 2007 9:58 PM, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
>   
>> If the licensing issue can't be resolved, it may be worth starting a
>> standalone project to handle coverage tests. 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 believe the author of coverage.py, Ned Batchelder, is on the list.
> Has he said whether he's willing to have Django include it without
> much hoop jumping?
>
> Todd
>
> >
>
>   

-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to