I've been looking around for how to make the django.contrib.auth User classe's "email" field to be unique and required. There are bunches of ways to do it, but it's just soooo darn easy to go into the source and change how the field is defined.
e.g. email = models.EmailField(_('email address'),unique=True)
But in my searches, I've read warnings that you should not do this. The reason, if it is given, is that you'll break your app if you update the contrib packages. But what if I work in virtualenvs and just leave the django version and packages intact for that particular app in that particular environment? What are the other practical and philosophical reasons for NOT editing the contrib source? Will I be smitten from the django community if I do so?
Thanks to all.
-- You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/YX9X8u9mdbwJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment