On Tue, 2009-08-04 at 09:22 -0400, George Vilches wrote: [...] > > Putting signals on a replacement CursorWrapper would give the same > functionality from a user standpoint (the ticket outright says "This > will enable all sorts of interesting and useful things, such as > logging and debugging functionality"),
It's like he's trying to sell you a used car. Further interrogation revealed that he wants one single feature, but dressed up this stepping stone as good for all mankind. You have to watch out for people like that. They're sneaky. :) > and already has some blessing. The patch will have to be brought up > to date, but I did address all of Malcolm's concerns at the time with > the most recent version of the patch, and the worries about signal > performance in #4561 have since been resolved. > > > What say you, Malcolm? :) I agree that things have moved on since the original ticket was opened and your patch looks quite decent and worth working out how to get it in. I'm on the record as agreeing with having a way to implement assertNumQueries() in the test framework. Unfortunately, this ticket doesn't solve Ivan's problem of the moment, as far as I can see. I can see after we create the 1.1.X, I'm going to be spending a bunch of time reading and applying patches with G. Vilches as the author. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
