On Oct 2, 12:09 pm, Ned Batchelder <n...@nedbatchelder.com> wrote: > I would think the same logic applies to Django. Nose needs to work with > lots of different projects, so they can't own the Django details, since > by that logic they'd also own the TurboGears logic, the Pylons logic, > the Twisted logic, etc... But the Nose plugin API isn't changing much > now, so Django could include a nose plugin which would only have to > change when Django details change. And we'd get all sorts of nose > features without having to implement them in the Django code.
That seems to make sense. I rather like the gesture here as well - shipping plugins that get Django to work well with other parts of the Python ecosystem sends a powerful message that Django wants to work well with other parts of the Python ecosystem. Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
