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 06/07/11 21:41, Daniel Swarbrick wrote:
> Or can we perhaps even add an option to FilePathField that would
> refresh the choices each time? I'm not entirely sure how that would
> work... proxy function maybe?
That sounds like a reasonable idea to me, since doing it by default
could impose a se
This problem was raised at least twice [1] [2] back in 2009 on django-
users, and neither post was answered.
If FilePathField is used declaratively for a form's field(s), it does
not get called for each instantiation of that form - only the first
time the form is used. Consequently, the choices ma
