Re: Django models should not contain 'evaluate' field/method since Django 1.1

[Łukasz Korzybski]

Sure,

The ticket: http://code.djangoproject.com/ticket/13640#preview

Greetings,
Lukasz

On May 25, 2:49 pm, Jacob Kaplan-Moss  wrote:
> On Tue, May 25, 2010 at 12:06 PM, naos  wrote:
> > I was migrating some django project recently from django 1.0.4 to 1.2.
> > In Django 1.2/1.1 I found that if model have 'evaluate' attribute then
> > one will get exception in admin edit page for that model if the page
> > contains inline forms with related models:
>
> [snip]
>
> This is a bug and should be fixed by fixing the hasattr() check. Can
> you open a ticket, please?
>
> Jacob

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Django models should not contain 'evaluate' field/method since Django 1.1

[Jacob Kaplan-Moss]

On Tue, May 25, 2010 at 12:06 PM, naos  wrote:
> I was migrating some django project recently from django 1.0.4 to 1.2.
> In Django 1.2/1.1 I found that if model have 'evaluate' attribute then
> one will get exception in admin edit page for that model if the page
> contains inline forms with related models:

[snip]

This is a bug and should be fixed by fixing the hasattr() check. Can
you open a ticket, please?

Jacob

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.