No! Unicode usernames is a bad idea. Usernames can be used for URLs,
paths and other technical stuff. Unicode usernames is a source of
unlimited potential bugs. It might be a good idea to add the unicode
'nickname' field that can be used instead of username in views - and
still use 'username' for usrls and paths. There's no Russian site that
would allow you to enter the login/username in Russian.

On 29 янв, 03:34, John Hensley <[EMAIL PROTECTED]> wrote:
> Usernames in django.contrib.auth are restricted to ASCII
> alphanumerics. Allowing Unicode seems fairly simple: compile the
> validator's regular expression with the re.UNICODE flag.
>
> To a Midwesterner with hardly any language competency beyond English,
> it seems like an obvious improvement -- surely everyone who builds
> Django sites in Russian or Chinese or Japanese would love to let
> people sign in with their real names. But I don't see much clamor
> about it, so I'm guessing there are good reasons this hasn't been
> done, or at least people have workarounds they're happy with.
>
> There was a fairly pessimistic thread on the users list back in 2005,
> the upshot of which was that people were used to being forced into 7-
> bit ASCII anyway, so you might as well not bother, or if you must,
> create another field in a user profile or something.
>
> What's the consensus on Unicode usernames? Is the current restriction
> intentional, or just left over from before the Unicode overhaul? Are
> the developers who could really use these (as opposed to those who
> just want to be courteous and future-proof) interested, or do you have
> other solutions you're happy with?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to