News for hackers. Stuff that matters.
Re:Django 1.2 final out on Monday by stevenwei on Saturday May 15, 2010 @09:17PM (#1351056)
Does this actually work?

It seems to me there would be a major bug since the existing auth.User email field definition is not unique and allows blank values, and this app doesn't do anything to check against that, nor does it do anything to remove the existing username field definition.

Re:Django 1.2 final out on Monday by jbox on Sunday May 16, 2010 @02:21PM (#1352482)
customizing auth.User to accept an email based login

This app solves the problem by allowing users to log in using their email address.

It's not a bug that it doesn't deal with account creation - it's outside the scope of the app.

That said, it is fairly trivial to create a registration form that enforces the constraints you mentioned.