Re: Extend support for long surnames in Django Auth

[James Pic]

Indeed first and last name dont make sense en various culture. In the
Memopol project for exampe where wé have a table of European Parliament
representative we have all sorts of names including (The Earl Of) name
suffix which is part of the reasons our first / last name system was
completely checkmated.

Nowadays I just go for a single and long name field and I would like to
suggest that django.contrib.auth takes this path too because the first name
and last name system isn't international and django is for building
websites on internet which is meant to be a communication tool connecting
Humans of the world, no matter if they have a first and last name or not.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CALC3KafvSRCm8O8%3Dgnps9ogCoxc9Fz4%3DxdhXCM_MPDN9fv0Wmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Extend support for long surnames in Django Auth

[Aymeric Augustin]

Hello,

I usually build my projects upon these recommendations, but the UX is awkward 
and the end result tends to be short_name = first_name and full_name = 
first_name + space + last_name.

We could discuss the usefulness of providing an alternate user model that has 
short_name + full_name instead of first_name + last_name but in my opinion 
that’s another discussion.

Best regards,

-- 
Aymeric.

> On 29 Jul 2016, at 17:55, ludovic coues  wrote:
> 
> The W3C have some recommandation on the question.
> 
> https://www.w3.org/International/questions/qa-personal-names
> 
> 2016-07-29 17:47 GMT+02:00 Aymeric Augustin
> :
>> Hello,
>> 
>> Indeed, Django’s default limit on last name length doesn’t work well for 
>> Brazilians (at least).
>> 
>> Actually having a `first_name` and `last_name` field doesn’t work well in 
>> various cultures, including the US when you want a middle initial. Custom 
>> user models are the general answer to that question.
>> 
>> In this particular case, the drawbacks of increasing the `max_length` of 
>> `first_name` and `last_name` to something like 50 seem limited now that we 
>> have the migrations framework. Making that change will automatically avoid 
>> the issue for many people — perhaps at the cost of introducing UI issues 
>> when the name is displayed in the header, but that’s arguably a lesser evil.
>> 
>> So I’m +0 on making that change.
>> 
>> --
>> Aymeric.
>> 
>>> On 29 Jul 2016, at 09:18, Raony Guimaraes Corrêa Do Carmo Lisboa Cardenas 
>>>  wrote:
>>> 
>>> Hello everyone,
>>> 
>>> For a long time I was having problems to login to djangopackages.com using 
>>> my github account (pydanny/djangopackages#338). After investigating I 
>>> discovered the problem was because my surname is longer than 30 characters. 
>>> I don't know why both first_name and last_name fields have the same size 
>>> limit of 30 characters in Django. That doesn't sound very reasonable.
>>> 
>>> I'm sure there are other people on the same situation and this already 
>>> happened with me trying to login in other django websites.
>>> 
>>> Tim Graham suggested I should first ask on this maillist 
>>> (https://github.com/django/django/pull/6988#issuecomment-235945422) to see 
>>> if there is consensus to make the change.
>>> 
>>> I would like to ask your opinion about an increase from 30 to 60 characters 
>>> on last_name field so that my login and others won't break again in the 
>>> future. I can create a Trac ticket if the response is positive.
>>> 
>>> Kind Regards,
>>> 
>>> 
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Django developers (Contributions to Django itself)" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to django-developers+unsubscr...@googlegroups.com.
>>> To post to this group, send email to django-developers@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/django-developers.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/django-developers/56bc25d9-372e-4985-b601-3cce9664160c%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Django developers  (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/4A15ED67-802B-4A3A-85DA-265A5A5ADEF1%40polytechnique.org.
>> For more options, visit https://groups.google.com/d/optout.
> 
> 
> 
> -- 
> 
> Cordialement, Coues Ludovic
> +336 148 743 42
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers  (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/CAEuG%2BTZXuGBr4_eU5pHBUONX8k5Z-z13YApJOxH%3D4iWbPutArA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to 

Re: Extend support for long surnames in Django Auth

[ludovic coues]

The W3C have some recommandation on the question.

https://www.w3.org/International/questions/qa-personal-names

2016-07-29 17:47 GMT+02:00 Aymeric Augustin
:
> Hello,
>
> Indeed, Django’s default limit on last name length doesn’t work well for 
> Brazilians (at least).
>
> Actually having a `first_name` and `last_name` field doesn’t work well in 
> various cultures, including the US when you want a middle initial. Custom 
> user models are the general answer to that question.
>
> In this particular case, the drawbacks of increasing the `max_length` of 
> `first_name` and `last_name` to something like 50 seem limited now that we 
> have the migrations framework. Making that change will automatically avoid 
> the issue for many people — perhaps at the cost of introducing UI issues when 
> the name is displayed in the header, but that’s arguably a lesser evil.
>
> So I’m +0 on making that change.
>
> --
> Aymeric.
>
>> On 29 Jul 2016, at 09:18, Raony Guimaraes Corrêa Do Carmo Lisboa Cardenas 
>>  wrote:
>>
>> Hello everyone,
>>
>> For a long time I was having problems to login to djangopackages.com using 
>> my github account (pydanny/djangopackages#338). After investigating I 
>> discovered the problem was because my surname is longer than 30 characters. 
>> I don't know why both first_name and last_name fields have the same size 
>> limit of 30 characters in Django. That doesn't sound very reasonable.
>>
>> I'm sure there are other people on the same situation and this already 
>> happened with me trying to login in other django websites.
>>
>> Tim Graham suggested I should first ask on this maillist 
>> (https://github.com/django/django/pull/6988#issuecomment-235945422) to see 
>> if there is consensus to make the change.
>>
>> I would like to ask your opinion about an increase from 30 to 60 characters 
>> on last_name field so that my login and others won't break again in the 
>> future. I can create a Trac ticket if the response is positive.
>>
>> Kind Regards,
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-developers+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/56bc25d9-372e-4985-b601-3cce9664160c%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django developers  (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/4A15ED67-802B-4A3A-85DA-265A5A5ADEF1%40polytechnique.org.
> For more options, visit https://groups.google.com/d/optout.



-- 

Cordialement, Coues Ludovic
+336 148 743 42

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAEuG%2BTZXuGBr4_eU5pHBUONX8k5Z-z13YApJOxH%3D4iWbPutArA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Extend support for long surnames in Django Auth

[Aymeric Augustin]

Hello,

Indeed, Django’s default limit on last name length doesn’t work well for 
Brazilians (at least).

Actually having a `first_name` and `last_name` field doesn’t work well in 
various cultures, including the US when you want a middle initial. Custom user 
models are the general answer to that question.

In this particular case, the drawbacks of increasing the `max_length` of 
`first_name` and `last_name` to something like 50 seem limited now that we have 
the migrations framework. Making that change will automatically avoid the issue 
for many people — perhaps at the cost of introducing UI issues when the name is 
displayed in the header, but that’s arguably a lesser evil.

So I’m +0 on making that change.

-- 
Aymeric.

> On 29 Jul 2016, at 09:18, Raony Guimaraes Corrêa Do Carmo Lisboa Cardenas 
>  wrote:
> 
> Hello everyone,
> 
> For a long time I was having problems to login to djangopackages.com using my 
> github account (pydanny/djangopackages#338). After investigating I discovered 
> the problem was because my surname is longer than 30 characters. I don't know 
> why both first_name and last_name fields have the same size limit of 30 
> characters in Django. That doesn't sound very reasonable.
> 
> I'm sure there are other people on the same situation and this already 
> happened with me trying to login in other django websites.
> 
> Tim Graham suggested I should first ask on this maillist 
> (https://github.com/django/django/pull/6988#issuecomment-235945422) to see if 
> there is consensus to make the change.
> 
> I would like to ask your opinion about an increase from 30 to 60 characters 
> on last_name field so that my login and others won't break again in the 
> future. I can create a Trac ticket if the response is positive.
> 
> Kind Regards,
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/56bc25d9-372e-4985-b601-3cce9664160c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/4A15ED67-802B-4A3A-85DA-265A5A5ADEF1%40polytechnique.org.
For more options, visit https://groups.google.com/d/optout.

Re: Extend support for long surnames in Django Auth

[Erik Cederstrand]

Hello Raony,

I'm sure I'm not aware of all the implications of changing the field length, 
but the first question should be "how long is long enough"? In answering this 
question, this Quora question comes to mind: 
https://www.quora.com/Why-are-South-Indian-names-often-long

Kind regards,
Erik
a.k.a. Bommiraju Sitaramanjaneyulu Rajasekhara Srinivasulu Laxminarayana Siva 
Venkata Sai :-)

> Den 29. jul. 2016 kl. 09.18 skrev Raony Guimaraes Corrêa Do Carmo Lisboa 
> Cardenas :
> 
> Hello everyone,
> 
> For a long time I was having problems to login to djangopackages.com using my 
> github account (pydanny/djangopackages#338). After investigating I discovered 
> the problem was because my surname is longer than 30 characters. I don't know 
> why both first_name and last_name fields have the same size limit of 30 
> characters in Django. That doesn't sound very reasonable.
> 
> I'm sure there are other people on the same situation and this already 
> happened with me trying to login in other django websites.
> 
> 
> 
> 
> 
> 
> 
> Tim Graham suggested I should first ask on this maillist 
> (https://github.com/django/django/pull/6988#issuecomment-235945422) to see if 
> there is consensus to make the change.
> 
> I would like to ask your opinion about an increase from 30 to 60 characters 
> on last_name field so that my login and others won't break again in the 
> future. I can create a Trac ticket if the response is positive.
> 
> Kind Regards,
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/56bc25d9-372e-4985-b601-3cce9664160c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/7FA7D68D-F718-404C-9F89-B4E1C3C8A6ED%40cederstrand.dk.
For more options, visit https://groups.google.com/d/optout.

Extend support for long surnames in Django Auth

[Raony Guimaraes Corrêa Do Carmo Lisboa Cardenas]

Hello everyone,

For a long time I was having problems to login to djangopackages.com using 
my github account (pydanny/djangopackages#338 
). After 
investigating I discovered the problem was because my surname is longer 
than 30 characters. I don't know why both first_name and last_name fields 
have the same size limit of 30 characters in Django. That doesn't sound 
very reasonable.

I'm sure there are other people on the same situation and this already 
happened with me trying to login in other django websites.


[image: selection_086] 



Tim Graham suggested I should first ask on this maillist 
(https://github.com/django/django/pull/6988#issuecomment-235945422) to see 
if there is consensus to make the change.

I would like to ask your opinion about an increase from 30 to 60 characters 
on last_name field so that my login and others won't break again in the 
future. I can create a Trac ticket if the response is positive.

Kind Regards,

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/56bc25d9-372e-4985-b601-3cce9664160c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.