#13121: Backwards compatible patch for ModelForm to improve model validation.
---------------------------------------------------+------------------------
          Reporter:  orokusaki                     |         Owner:  nobody  
            Status:  closed                        |     Milestone:          
         Component:  Database layer (models, ORM)  |       Version:  1.2-beta
        Resolution:  duplicate                     |      Keywords:          
             Stage:  Unreviewed                    |     Has_patch:  1       
        Needs_docs:  0                             |   Needs_tests:  0       
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Comment (by orokusaki):

 '''Sigh'''

 If this is how the Django community values bug fixes, than I won't bother
 from now on. I have already caught a critical bug in the model validation
 before, and it was quickly fixed. I don't see what the difference is. Is
 it just because this one isn't critical. It just makes you give up a
 feature, so that's not important?

 I'm sure that you have more than just the lack-of-process as a means for
 dismissing this bug fix as banter. If I owned a automotive shop, and a
 person brought me their manual and said "It says that the cigarette
 lighter gets hot, but it's not working", I wouldn't simply tear the page
 out of the manual and say "There, now it does just what the manual says.".
 The documentation was not the issue. The code was, and blithering about
 bureaucratic processes won't change that. I practically wrote a
 Wikipedia.org article about this, and your complaint is that of a lack of
 due diligence. I don't know how to make a diff, and I haven't really used
 unit testing (however, this code will not break already existing module-
 level tests). The code was documented exactly as needed. I just know
 enough to find the bugs, and I thought that might be some help to an open
 source community. I guess I'm wrong. I'll leave this closed instead of
 fighting my case, but if you change your mind and there is something I can
 do to help (aside from a diff or unit test), please let me know and I will
 do it right away.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/13121#comment:5>
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