On Wed, Oct 13, 2010 at 12:47 AM, alekam <kame...@gmail.com> wrote: > Hi All, > > I found very useful ticket #8054. This ticket has accepted status and > assigned to brosher about 2 years. The problem describes on ticket > detail page and in the wiki http://code.djangoproject.com/wiki/ListColumns > The ticket has patch witch passes all existing regression tests and I > plan to write unit tests for it. > It is real to add ticket #8054 to 1.3 milestone?
I've looked at the wiki and ticket, and I'm having difficulty seeing what benefits this proposal offers. It looks to me like you're proposing to change the syntax that is used to declare list_display, but I can't really see any signficant changes in the flexibility of the new approach. As far as I can make out, everything you describe (and more) can already be achieved by using callables in list_display. This patch isn't going to get added to trunk just so we can add a new syntax for things we can already do. It needs to clearly add new capabilities that don't currently exist. 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.
