On 7/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Now - that's what I call a convincing reason to switch.
I'm still hesitant to make the _default_ testing scheme dependent on an external package, simply because Django doesn't have any dependencies on anything other than the Python core libraries and a DB integration library.
However, if you look at the patches that I have submitted, the approach I have taken allows end users to configure their own testing scheme to be invoked by './manage.py test'. If there are utilities or a 'nose run_test' implementation that we can add to a ' django.test.nose' package, then adding nose testing will be as simple as installing nose and changing a configuration setting for the site.
Russ Magee %-)
> It makes coverage reports? And they work with Django? Whow!
Sure.
Now - that's what I call a convincing reason to switch.
I'm still hesitant to make the _default_ testing scheme dependent on an external package, simply because Django doesn't have any dependencies on anything other than the Python core libraries and a DB integration library.
However, if you look at the patches that I have submitted, the approach I have taken allows end users to configure their own testing scheme to be invoked by './manage.py test'. If there are utilities or a 'nose run_test' implementation that we can add to a ' django.test.nose' package, then adding nose testing will be as simple as installing nose and changing a configuration setting for the site.
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
