The patches on this ticket will not land for 1.2. That ticket
contains a series of very large patches, and I don't think a firm
design decision has ever been made about the status of that ticket,
and it was never on the 1.2 feature list.
"I disapprove of what you say, but I will defend to the death your
right to say it." -- Voltaire
"The people's good is the highest law." -- Cicero
"Code can always be simpler than you think, but never as simple as you
want" -- Me
Ok, I'll update the ticket.
On Feb 4, 7:08 pm, Alex Gaynor <alex.gay...@gmail.com> wrote:
> On Thu, Feb 4, 2010 at 11:06 AM, Adam Nelson <a...@varud.com> wrote:
> > I don't suppose there's any way to get the patches from ticket #3591
> > into Django 1.2? If not, can it be marked as definitively not in 1.2
> > so I can roll a custom solution for myself? It's always hard to tell
> > from the ticket details what stage tickets like that are in.
> > Thanks,
> > Adam
> > --
> > You received this message because you are subscribed to the Google Groups "Django developers" group.
> > To post to this group, send email to django-d...@googlegroups.com.
> > To unsubscribe from this group, send email to django-develop...@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/django-developers?hl=en.