It sounds like the concern here are repetitive and untidy lines with
lots of "verbose_name" so use of positional arguments may prettify a
bit field definitions. It is not obvious from documentation (all
fields are listed alphabetically) but for all except relationship
fields verbose_name is the fir
Hi all,
I've been looking into a few old unresolved issues.
http://code.djangoproject.com/ticket/11667
"Full traceback if import error before model validation" is a simple
annoyance. On the issue page (one year old) various solutions are
suggested, each with a patch. Can someone take a decision o
On 14 January 2011 16:22, Marco Paolini wrote:
>
> then maybe a new special attribute like "dont_call_me" or
> "i_will_call_you_if_needed" (way more polite)
>
> could be handy in this situations? What do you think?
I think it's too much of a corner case to justify another check in lookup.
When I
bpeschier ha scritto:
what if you add an alters_data class attribute to your ModelForm subclass?
class MyForm(ModelForm):
alters_data = True
this way __call__ is not going to get called...
No, but it will be replaced with settings.TEMPLATE_STRING_IF_INVALID.
See:
http://code.djan
> what if you add an alters_data class attribute to your ModelForm subclass?
> class MyForm(ModelForm):
> alters_data = True
>
>
> this way __call__ is not going to get called...
No, but it will be replaced with settings.TEMPLATE_STRING_IF_INVALID.
See:
http://code.djangoproject.com/brows
bpeschier ha scritto:
I am agreeing with the changes as made in [14992] as they make things
more consistent. The snag I run into was a flexible filter for making
ModelForm-instances which took a form-class as an argument via a
Variable. Since classes are callable (their constructor), suddenly I
h
On Fri, Jan 14, 2011 at 10:28 PM, Sayane wrote:
> There is a problem with TemplateResponse and request.urlconf. Custom urlconf
> is removed[1] before TemplateResponse is rendered[2]. This means that any
> call to reverse() when rendering template will use default urlconf (from
> settings). This ma
On Fri, Jan 14, 2011 at 10:00 PM, Klaas van Schelven
wrote:
> Hi,
>
> A lot of my models look like this
>
> class MyModel(models.Model):
> some_field = models.IntegerField(verbose_name=_("Some field"))
> some_other_field = models.IntegerField(verbose_name=_("Some other
> field"))
>
> clas
There is a problem with TemplateResponse and request.urlconf. Custom urlconf
is removed[1] before TemplateResponse is rendered[2]. This means that any
call to reverse() when rendering template will use default urlconf (from
settings). This makes TemplateResponse useless when using custom urlconf.
I am agreeing with the changes as made in [14992] as they make things
more consistent. The snag I run into was a flexible filter for making
ModelForm-instances which took a form-class as an argument via a
Variable. Since classes are callable (their constructor), suddenly I
had a bunch of instances
Hi,
A lot of my models look like this
class MyModel(models.Model):
some_field = models.IntegerField(verbose_name=_("Some field"))
some_other_field = models.IntegerField(verbose_name=_("Some other
field"))
class Meta:
verbose_name = _("My model")
verbose_name_plural =
On 14 January 2011 13:17, Stas Malolepszy wrote:
> On Friday, January 14, 2011 3:25:18 AM UTC+1, Russell Keith-Magee wrote:
>>
>> Ticket #15075 was opened to cover the regression you describe; Luke
>> closed that ticket by committing r15196 and r15197.
>>
>> Its not clear to me if Luke has done th
On Friday, January 14, 2011 3:25:18 AM UTC+1, Russell Keith-Magee wrote:
> Ticket #15075 was opened to cover the regression you describe; Luke
> closed that ticket by committing r15196 and r15197.
>
> Its not clear to me if Luke has done this in response to your email,
> or if it's just coincidenc
13 matches
Mail list logo
