On 10 November 2011 18:53, hcarvalhoalves wrote:
> I believe the solution is to actually figure a migration path to move
> everything that is non-essential to outside the User model. To
> identify a User, it should be enough to have username, password and
> permissions, and have the rest of the fi
This is a harder problem then just that. While doing that would allow a
solution to the name problem, there are more problems django.contrib.auth's
User model and it would be best to come up with a generic solution that fixes
all of these problems, instead of applying bandaid fixes.
On Thursday
I believe the solution is to actually figure a migration path to move
everything that is non-essential to outside the User model. To
identify a User, it should be enough to have username, password and
permissions, and have the rest of the fields live in a
django.contrib.auth.models.DefaultUserProfi
On Thu, Sep 22, 2011 at 1:52 PM, Aymeric Augustin
wrote:
> 2011/9/22 lvella :
>> What about changing this in future versions? Maybe simply a
>> "true_name" field would do? Or maybe a way to customize the fields in
>> the User model.
>
> Hi lvella,
>
> This issue should be viewed in the context of:
2011/9/22 lvella :
> What about changing this in future versions? Maybe simply a
> "true_name" field would do? Or maybe a way to customize the fields in
> the User model.
Hi lvella,
This issue should be viewed in the context of:
https://code.djangoproject.com/wiki/SummerOfCode2011#Enhancedauth.us
The User model included in Authentication subsystem is very annoying
to use here in Brazil. The common "first name" and "last name" method
of identifying people found in English speaking countries is very
unnatural to our culture, which people usually have two or more family
names. It is a cultural
