On Tue, Dec 16, 2008 at 1:16 AM, David Reynolds <[email protected]> wrote: > > Hi, > > I've been attempting to keep this ticket inline with trunk for quite a > while and it would be useful to get some feedback on it, or start up a > discussion as to how it can move forward. Russell mentioned a while > ago that it could integrate with #4656. Is that still possible?
>From an initial inspection, #5610 looks ready for trunk. The feature is well defined, and the patch now has docs and tests. I'm knee deep in aggregation code at the moment, but I'll put this on my todo list. The connection with #4656 is that once you can single out an individual model to dump, you will want to dump all the dependencies of that model. Obviously, you could do this by manually specifying all dependent model names, but providing an easy option to hunt down dependencies would also be handy. That said, I consider #4656 and #5610 to be separate issues. An absence of a fix for #4656 won't stop me committing your patch for #5610. 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 [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 -~----------~----~----~----~------~----~------~--~---
