Re: Shouldn't custom fields in ModelForms pick up model Field options by default?

> > Thanks, the accompanying discussion is very interesting and on point. > > But as someone there points out, why stop at widgets? > > Because customizing widgets is a common request, unlike other attributes. But customizing fields is quite common, no? I agree that it's rare that you will want

Re: Ticket #7539 (ON DELETE support) in Django 1.2?

Michael Glassford wrote: > > > hcarvalhoalves wrote: >> On Aug 14, 11:48 pm, Russell Keith-Magee >> >> wrote: >>> On Sat, Aug 15, 2009 at 8:09 AM, >>>

Re: Ticket #7539 (ON DELETE support) in Django 1.2?

On Sat, Aug 15, 2009 at 10:46 PM, Michael Glassford wrote: > > Russell Keith-Magee wrote: >> On Sat, Aug 15, 2009 at 10:57 AM, Michael Glassford >> wrote: >>> Russell Keith-Magee wrote: On Sat, Aug 15, 2009 at 8:09 AM,

Re: Ticket #7539 (ON DELETE support) in Django 1.2?

Russell Keith-Magee wrote: > On Sat, Aug 15, 2009 at 10:57 AM, Michael Glassford > wrote: >> Russell Keith-Magee wrote: >>> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves >>> wrote: On Aug 13, 9:30 am, Russell Keith-Magee

Re: admin reuse

On Aug 15, 9:14 pm, Russell Keith-Magee wrote: > On Sat, Aug 15, 2009 at 3:52 PM, Haroldo > > Stenger wrote: > >  I've seen the admin evolve to very sophisticated user interaction. > > Nonetheless, the param to  HttpResponse() when a model object

Re: Ticket #7539 (ON DELETE support) in Django 1.2?

On Sat, Aug 15, 2009 at 10:57 AM, Michael Glassford wrote: > > Russell Keith-Magee wrote: >> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves >> wrote: >>> On Aug 13, 9:30 am, Russell Keith-Magee >>> wrote: On Thu, Aug

Re: admin reuse

On Sat, Aug 15, 2009 at 3:52 PM, Haroldo Stenger wrote: >  I've seen the admin evolve to very sophisticated user interaction. > Nonetheless, the param to  HttpResponse() when a model object has been > saved, is hardcoded and most of the times "../../.." or "../.."  (see

Re: Django settings paths mess

On Aug 15, 6:42 pm, Yuri Baburov wrote: > On Sat, Aug 15, 2009 at 12:24 PM, Graham > > > > > > Dumpleton wrote: > > On Aug 15, 1:15 pm, Yuri Baburov wrote: > >> Hi all, > > >> I'm trying to figure out correct overall and

Re: App Engine support

Hi Malcolm, first of all, we'll soon start with a few experiments and since you wanted to play around with some code, too, could you please tell us your bitbucket username, so we can give you write access to the repository? On Aug 11, 4:07 am, Malcolm Tredinnick wrote:

Re: overriding queryset for admin inlines

...would get via the actual Python API? In this case, you couldn’t switch the managers around either. On Aug 15, 10:19 am, Zachary Voase wrote: > Correct me if I’m wrong, but won’t the inlines display the actual > relationship that you > > On Aug 14, 5:43 pm, smcoll

Re: overriding queryset for admin inlines

Correct me if I’m wrong, but won’t the inlines display the actual relationship that you On Aug 14, 5:43 pm, smcoll wrote: > Currently, we can override the queryset used by ModelAdmins.  This is > helpful, since often times the default manager omits instances that >

Re: Shouldn't custom fields in ModelForms pick up model Field options by default?

> Please file a ticket for the documentation fix it would be greatly   > appreciated. :-) Will do. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: Shouldn't custom fields in ModelForms pick up model Field options by default?

In terms of backward compatibility, perhaps there could be a new keyword argument to Field, something like with_model_defaults, that the user would use to indicate a desire to get the attributes from the Model. How would this work? Maybe something like this (this is just a sketch):

Re: Django settings paths mess

On Sat, Aug 15, 2009 at 12:24 PM, Graham Dumpleton wrote: > On Aug 15, 1:15 pm, Yuri Baburov wrote: >> Hi all, >> >> I'm trying to figure out correct overall and settings path usage >> strategy for my Django applications. >> What I am experiencing

admin reuse

I've seen the admin evolve to very sophisticated user interaction. Nonetheless, the param to HttpResponse() when a model object has been saved, is hardcoded and most of the times "../../.." or "../.." (see options.py in contrib.admin). Being able to change that string by some means of