On Aug 9, 8:41 am, andybak wrote:
> It does get slightly uglier when you have cases such as:
> f = CharField(choices=zip
> (some_complex_expression_that_generates_a_list,
> some_complex_expression_that_generates_a_list))
>
> You don't really want to assign the expression to a variable within
> yo
Sorry to bring this discussion back to the original topic...
http://code.djangoproject.com/ticket/9498 is a pretty serious
regression for us, which will prevent us upgrading to 1.0.1. There is
a patch, and I've just added some tests - is there any chance this
will make it into the release?
Thank
On 26 Feb, 04:56, "James Bennett" <[EMAIL PROTECTED]> wrote:
> If there's a bug that's been annoying the heck out of you and you want
> it fixed before the release, this would be the time to speak up about
> it.
Because you did ask, the one that's annoying me most at the moment
(and preventing me
Honza Král wrote:
> Hi all,
> in django.contrib.admin.ChangeList.get_filters
> there is a line:
>
> if self.lookup_opts.admin.list_filter and not
> self.opts.one_to_one_field:
>
> does anybody know why there is the second part of the condition?
> when I commented the second part out, the
