On Fri, May 6, 2011 at 1:28 AM, legutierr wrote:
>
>> There are plenty of other workarounds -- the easiest is to note the
>> email field is optional and just create a RealUserEmail object with a
>> OneToOne to User. Given that, a hacky workaround in Django itself just
>>
> There are plenty of other workarounds -- the easiest is to note the
> email field is optional and just create a RealUserEmail object with a
> OneToOne to User. Given that, a hacky workaround in Django itself just
> isn't going to happen. The right thing to do is to get the auth
> refactor done
On Thu, May 5, 2011 at 9:08 AM, Yishai Beeri wrote:
> Wouldn't it be possible to work around this, even for the time being, by
> having auth.User read a SETTING to use as the default max_length (defaulting
> of course to the old 75)?
No, for any number of reasons. Primary
Wouldn't it be possible to work around this, even for the time being, by
having auth.User read a SETTING to use as the default max_length
(defaulting of course to the old 75)?
Hardly the prettiest solution, but given the right name
(AUTH_EMAIL_MAXLEN_HACK, anyone?) and documentation it can
On Thu, May 5, 2011 at 8:06 AM, Patryk Zawadzki wrote:
> This problem is now more severe due to Facebook returning proxied
> e-mail addresses in this format:
>
> apps+111.22.abcdef0123456789abcdef0123456...@proxymail.facebook.com
Unfortunately, the
On Thu, Feb 18, 2010 at 1:15 AM, Artem Skvira 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
> Addressing the limitations of the builtin auth.User is something I
> hope to look at in the 1.3 timeframe.
In that case, would it be reasonable to have an open ticket for the
specific request of being able to customize the length of the email
field in the contrib.auth User object?
I'm guessing
On Thu, Feb 18, 2010 at 8:15 AM, Artem Skvira 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
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