>
>
>
> On Tuesday, March 20, 2012 7:08:49 AM UTC-7, Tom Evans wrote:
>
>> On Tue, Mar 20, 2012 at 1:37 PM, Russell Keith-Magee
>> <russel> wrote:
>> >
>> > On 20/03/2012, at 8:38 PM, Tom Evans wrote:
>>
>>
>> > Personally, I'd be in favor of option (3), mostly because what the last
>> 6 years has taught us is that no matter what we pick as field names/sizes,
>> *someone* will be unhappy. However, I won't get too bent out of shape if
>> Django ends up shipping at least 1 new concrete User model -- at the very
>> least, it's a good way to prove we can eat our own dogfood.
>>
>> Right. So the conclusion to this is "Ship broken, allow people to fix it".
>>
>> Tom - did you read the paragraph that follows? It seems to me to say
that by default - new projects would get the improved auth model, because
they would be specifying the app with the new app loading approach.
Doesn't that solve your main problem?
>
>
>> >
>> > If we introduce 1-N new User classes, we could also take the
>> opportunity to make one of the new User models the default user if you
>> deploy auth using an App definition, but User the default otherwise. This
>> means that any new projects would get the new SimpleUser class, but
>> existing projects would get the older User class.
>>
>
>
>
>
>
>> >
>> > 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.
-Preston
PS most email clients should handle wrapping on the reading end, your
emphasis on this technical detail feels out of place.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/t45LV8LL9B8J.
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.
