I wanted to get some feedback from the mailing list about a patch I wrote. There are two approaches I tried, and attached them both to this ticket:
http://code.djangoproject.com/ticket/10314 Quick explanation: Basically, the assertFoo methods in the python stdlib test case class accept a "msg" parameter, to customize the failure message given. The methods like this in django do not accept this parameter to pass it along. I think they should, and I gave an example in the ticket. The ticket was originally closed as invalid by sebleier. The reason he gave is that the django assertFoo methods can fail in a variety of ways, whereas the python assert methods can only fail in one way. While this is an important thing to keep in mind when writing test cases, I still think that it is useful to be able to customize the error message, so I wrote the patch. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
