On Thu, Feb 18, 2010 at 1:15 AM, Artem Skvira <artem.skv...@gmail.com> wrote: > Hi all, > > Following the django's tracker policy I'dlike to discuss this issue > here instead of re-opening the ticket (http://code.djangoproject.com/ > ticket/12900#comment:1) > > My problem with current limitation of 75 characters is that it does > not allow me to use auth.User.email for storage of login details. > While there's certainly a workaround (using custom profile model) I am > wondering what are the potential problems with the change to auth.User > itself and why it might not be backwards compatible for existing > django applications already using this field in User?
This problem is now more severe due to Facebook returning proxied e-mail addresses in this format: apps+111111111111111.2222222222.abcdef0123456789abcdef0123456...@proxymail.facebook.com -- Patryk Zawadzki I solve problems. -- 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.
