On Thu, Jun 3, 2010 at 4:23 PM, Matt Hoskins <skaffe...@googlemail.com> wrote: > I haven't had a reply to this, which could have been bad timing > posting it around when the conference was happening, or it could be as > I gave the background first rather than summarising what I was after > first so people skipped over reading it :).
It's probably more the former than the latter; I'm still working through the disaster that is my Post-DjangoCon inbox :-) If it makes you feel any better, your original mail was on my list of things to look at. There's also a small dose of "exhausted after the 1.2 final push" - those in the core team that weren't at DjangoCon are taking a short break from proceedings to recuperate. > The ticket's languished for a couple of years now - I've submitted > what I think is a better patch on the ticket and included some tests > in the patch, but I've not previously done any work on Django before > and it could do with someone more versed in the postgresql back-end > for Django to take a look at it and advise me on how to get the ticket > moved along (and whether my tests are sufficient and in a good enough > place in the test suite). I've just given your patch on #8901 a quick inspection, and it looks good enough to me to progress to RFC (which I've done). I'm hoping to have some time tonight to commit some patches; I'll try to put this on the list. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
