On Fri, Apr 12, 2013 at 8:54 AM, Gustavo Narea <[email protected]> wrote: > So I guess that means that it won't be considered for inclusion in Django? > If so, I'll close that ticket.
Hm, I wouldn't be so hasty -- it's something I, at least, would like to include. Of course, the concerns about the implementation are still there, and they're non-trivial. So my actual yes/no would be based more on the concrete proposal. But I think it'd be a good idea to include in core *if* it can be done well. I know it's a lot to ask given the mixed messages so far, but would you be OK preparing a patch/pull request for us to discuss? Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
