On Wednesday, July 6, 2011 2:30:12 AM UTC+12, Gregor Müllegger wrote:
>
> Hi, Chris.
>
> Seems that I'm now unemployed as GSoC Student,
> looks like you already did all the work! ;-)
>
I prefer to show prototype code than just discussing things. It's more fun
:)
> Besides this, great work. If
I have a formset in my application where there is a select field and
also a multiselect field in a form. In some object edit view, number
of times each form in the formset gets called increases with the
increase of number of relationships between objects in the db(see my
question on stackoverflow -
On Jul 7, 1:04 am, Luke Plant wrote:
> That sounds like a reasonable idea to me, since doing it by default
> could impose a serious performance hit. In it's most naive form (i.e.
> making the 'choices' attribute a lazy list using
> django.utils.functional.lazy) this wouldn't be too hard to impleme
On Jul 6, 1:11 pm, Michal Petrucha wrote:
> Hmm, this is exactly what I had in mind when thinking about this
> problem. I see that even despite keeping the changes to a minimum, the
> patch looks quite big. I'll definitely review this once I start
> working on relationship fields.
No wonder the
I'd like to raise the topic of exception handling in templates, to see
what people think of the current state and discuss possible
improvements.
I personally find it confusing to use and create template tags at
times, due to exception handling. Sometimes exceptions are supposed to
be silenced, and
