#12991: Django 1.2 should have optional support for unittest2
----------------------------------------+-----------------------------------
          Reporter:  ericholscher       |         Owner:  PaulM
            Status:  assigned           |     Milestone:  1.3  
         Component:  Testing framework  |       Version:  SVN  
        Resolution:                     |      Keywords:       
             Stage:  Accepted           |     Has_patch:  1    
        Needs_docs:  1                  |   Needs_tests:  0    
Needs_better_patch:  0                  |  
----------------------------------------+-----------------------------------
Comment (by PaulM):

 One possible backwards compatibility issue this brings up is in user
 tests. Because unittest2 changes error reporting to be more verbose, users
 who are doing the wrong thing and have written tests which compare against
 exact, specific error strings (as was done in
 test_client_regress/models.py), there is a possibility that some user
 unittests may not work after this patch. This problem is introduced at the
 python level, and it seems that the general Django policy is not to
 support users who are doing the wrong thing.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/12991#comment:9>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to