Scott Bradley

Looking into this a bit more. I think I see -- what you are saying is that by including the multimail URLs, this includes the set-as-primary URL which exposes that...

So, the email property used to be unique_together with user. I could not recall the use case for that setup, and it seemed to me that Email addresses should be...

@clemente sorry it's been a while. I'd like to get this issue cleaned up. If I understand correctly, if we were to have it that the user and email were...

I am trying to understand the scenario whereby the email address on a given User object matches an existing multimail EmailAddress object for a different user. Do you know why...

I agree that the logic is overly complicated. I am concerned about complicating it more. The reason this is here is that pre-django 1.5, the shell would enforce an email...

_Edit: looking at Django's User code, I am no longer sure if this is the best approach. See further comments below._ What I think is this: The whole of the...

Well, now I am looking at the Django code for the User model, and I notice this: email is marked blank=True, but the following is also indicated: `REQUIRED_FIELDS = ['email']`...

Ok, I've dug into this a bit. Based on what I am seeing in the docs here: https://docs.djangoproject.com/en/1.7/topics/auth/customizing/#django.contrib.auth.models.CustomUser.REQUIRED_FIELDS, and on some quick checks against different versions of Django -- it...

Ok, I had forgotten that the user creation process depends on that signal to create the EmailAddress object when a user is originally created. Furthermore, the demo code relies on...