Hey JJ, And I probably could have been less gruff.
What I was trying to say was, as someone that's been hanging in these parts for a few years now, I can tell you that it is unlikely the devs would introduce it to standard Django. That's why the BaseUser is so base - it's specifically designed to be extenisble and easily replaced, and that type of functionality - and you are very right here - is probably needed by many, but not by every. And as such, is a perfect candidate for an app or extension rather than inclusion in the base. See Django Debug toolbar, or REST frame work or model-utils or any number of other very useful apps - essential and invaluable for some, not needed by all. On another note, FYI there is an URLField that could be used on athleteurl https://docs.djangoproject.com/en/1.7/ref/models/fields/#urlfield or you could just create a slug per Athlete and then refer to each Athlete by the get_absolute_url function? (I don't know if you've done this and rejected it - but it's what I'd do straight up). https://docs.djangoproject.com/en/1.7/ref/models/instances/#get-absolute-url cheers L. On 2 December 2014 at 13:37, JJ Zolper <jzth...@gmail.com> wrote: > Lachlan, > > Thanks for your input. I apologize if from my OP that it wasn't clear but I > am already creating a Profile or "extending the user model". > > # Athlete User > > class Athlete(models.Model): > > athleteuser = models.OneToOneField(User) > > athleteavatar = models.ImageField("Profile Pic", upload_to="images/", > blank=True, null=True, default='images/default/no-img.jpg') > > athletebirthday = models.DateField(blank=True, null=True) > > athleteurl = models.CharField(max_length=30, unique=True, blank=True) > # Must limit to a-z && A-Z && and 0-9 chars, validators=[validate_slug] > > athletelanguage = models.CharField(max_length=15, blank=True) > > athletecommunities = models.ManyToManyField('communities.Community', > blank=True, null=True) > > athletecolleges = models.ManyToManyField('colleges.College', blank=True, > null=True) > > athletetwitterscreenname = models.CharField(max_length=30, blank=True) > > isVerified = models.BooleanField(default=False) > > > > User.profile = property(lambda u: > Athlete.objects.get_or_create(athleteuser=u)[0]) > > > Certainly because Django is so flexible a multi email field doesn't have to > be native but I was more just getting a feel for any interest that others > might have in having this capability available. To me it is a very standard > use case, and again to me off the top of my head my opinion is that > something that solves this use case could be a standard feature that is > shipped, that's really all this is about. > > For the time being I am trying basically your route and am doing things as > an extension of what already exists. > > Thanks a lot, > > JJ > > > On Monday, December 1, 2014 8:05:41 PM UTC-5, Lachlan Musicman wrote: >> >> You don't really need it native in Django because the User Model is >> easily extensible - giving you or others the opportunity to extend it >> as you see fit and to release it the world as fle has. >> >> See here: >> >> >> https://docs.djangoproject.com/en/1.7/topics/auth/customizing/#extending-the-existing-user-model >> >> >> cheers >> L. >> >> On 2 December 2014 at 11:58, JJ Zolper <jzt...@gmail.com> wrote: >> > Hey everyone, >> > >> > I'm just curious if anyone around the community has an interest in >> > discussing the possibility of adding a "MultiEmailField" to Django? >> > >> > Here is what I found when roaming the internet: >> > >> > https://github.com/fle/django-multi-email-field >> > >> > Basically, the reason I care is because on my website I'm building the >> > ability to manage multiple e-mails on the user's profile. So on sites of >> > the >> > caliber of facebook, google, twitter, and so on allow a person to have >> > multiple e-mails listed. Then for example select which one they want to >> > be >> > their "primary" e-mail. My thoughts would be then which ever one my user >> > selects I would copy that selection from the "multiple email field >> > management view" to the django.auth.user "email" field. So basically >> > whatever they pick on my management for multiple emails set that to the >> > default email field on a Django user. That way for my code that uses the >> > django auth user email field for login handling (with the password) it >> > can >> > verify if it shall allow that user to login. Again, this primary email >> > is >> > the center of the entire users interaction in terms of authentication >> > and I >> > am aiming to show them say a check mark next to which one they have >> > chosen. >> > The rest of the e-mail addresses could serve other purposes. For sites >> > like >> > facebook, google, etc they could be recovery email addresses, but for me >> > I >> > would check the extensions. So for what I'm doing I would check within >> > the >> > list of emails the user has if say it has the "vt.edu" extension if they >> > were trying to join a college community and so on. >> > >> > So I think by now I've explained my reasoning behind wanting some sort >> > of >> > multiple email field. I would use it to set which email is the primary >> > as >> > well as allow them to add multiple emails to then verify their >> > identities >> > but also use some for recovery of an account for example. >> > >> > Does anyone agree with me that they would like to see this functionality >> > native in Django? >> > >> > Thanks for your time, >> > >> > JJ Zolper >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Django users" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to django-users...@googlegroups.com. >> > To post to this group, send email to django...@googlegroups.com. >> > Visit this group at http://groups.google.com/group/django-users. >> > To view this discussion on the web visit >> > >> > https://groups.google.com/d/msgid/django-users/c206b3ed-c434-456d-b978-b7fe67c8d0bd%40googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> You have to be really clever to come up with a genuinely dangerous >> thought. I am disheartened that people can be clever enough to do that >> and not clever enough to do the obvious thing and KEEP THEIR IDIOT >> MOUTHS SHUT about it, because it is much more important to sound >> intelligent when talking to your friends. >> This post was STUPID. >> >> ----------------------------------------------------------------------------------------------------------- >> The Most Terrifying Thought Experiment of All Time >> >> http://www.slate.com/articles/technology/bitwise/2014/07/roko_s_basilisk_the_most_terrifying_thought_experiment_of_all_time.html > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/e9001bd9-8823-41f2-921f-e9924d5e81f2%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- You have to be really clever to come up with a genuinely dangerous thought. I am disheartened that people can be clever enough to do that and not clever enough to do the obvious thing and KEEP THEIR IDIOT MOUTHS SHUT about it, because it is much more important to sound intelligent when talking to your friends. This post was STUPID. ----------------------------------------------------------------------------------------------------------- The Most Terrifying Thought Experiment of All Time http://www.slate.com/articles/technology/bitwise/2014/07/roko_s_basilisk_the_most_terrifying_thought_experiment_of_all_time.html -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAGBeqiP1t%3Da3P1bqrgnnstBmJnCLhqSUDZrtkOd4nrdtpZ2utA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
