On 21/03/2012, at 4:57 AM, ptone wrote:
> >
> > The key point here is that we're not forcing every Django user to discover
> > by accident that they need to run an ALTER TABLE statement in order for
> > their projects to keep working. The opt-in nature of the change is key.
>
>
>
>
>
> I think the key is that if
>
> INSTALLED_APPS = (
> ...
> 'django.contrib.auth'
> )
>
> then user model is the old one
>
> but if
>
> INSTALLED_APPS = (
> app('django.contrib.auth' )
> )
>
> then auth model is an improved concrete class
>
> If I'm understanding the meaning of an "App definition"
>
> I basically agree with your main point, Django should ship the improvement as
> the new default, which isn't mutually exclusive with keeping backwards compat.
IIRC, the exact syntax is slightly different, but you've got the right idea.
Yours,
Russ Magee %-)
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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.
