Re: (Model)Forms localize=True violates DRY

I have opened a ticked for this same issue, it was rejected because the core team didn't liked the idea of including FormField options in ModelField. Decision i think was correct, I wasnt aware the other FormFields options in ModelFields like help_text were there for historical reasons.

Re: Reg Memcache issue.

On 22/06/12 19:08, Ramesh-Nivista wrote: > Hi, > > We are facing one issue when we tried to update the memcache module. > Please check below our issue which is explained indetail. > > > We tried to deploy our django application and whenever we access a > particular content based page( a page

Reg Memcache issue.

Hi, We are facing one issue when we tried to update the memcache module. Please check below our issue which is explained indetail. We tried to deploy our django application and whenever we access a particular content based page( a page which fetches the data from DB) we are facing cache time

Re: (Model)Forms localize=True violates DRY

On Fri, Jun 22, 2012 at 7:23 AM, Klaas van Schelven < klaasvanschel...@gmail.com> wrote: > I've created a ticket, but have always understood that calling > attention to tickets should be done separately on the Django- > developers mailinglist It's not necessary nor encouraged to call attention

Re: Plans for "forms"

Thanks for the info On Jun 21, 2:04 pm, Andrew Godwin wrote: > On 21/06/12 11:58, Klaas van Schelven wrote: > > > Hi all, > > > I'm not entirely sure about the forum to ask this question: the > > motivation is "django-users" like; but since it's about a roadmap / > > the

(Model)Forms localize=True violates DRY

Hi all, I've created a ticket, but have always understood that calling attention to tickets should be done separately on the Django- developers mailinglist, so allow me to copy/paste a bit: As it is now one cannot make localized ModelForms without violating DRY. Developers w/o the desire for