To me, it boils down to something quite simple. Django's built-in auth
system uses usernames for identifying users, and email addresses as a
way to communicate with those users.
Yes, it might well be better for some sites to use email addresses as
the username, but in those cases, you would want
Hi all.
I've read all content of previous thread [1] and saw that it had come
to discussion about pre_create. One solution to resolve trouble with
doing something after creation is proposed by Amit Upadhyay (catch
both pre_ and post_save and set some property - is_new - in pre_save),
but it have
On Jul 5, 12:48 pm, anna <[EMAIL PROTECTED]> wrote:
> Just in case anyone knows, is it the same with the other frameworks
> for Python, like Pylons, Turbogears, etc? I'm thinking yes, based on
> your answers here, but just wondering.
>
As someone coming to Django from TurboGears, I can say tha
On Wed, 2007-07-04 at 12:12 -0500, Adrian Holovaty wrote:
> On 7/4/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > Oh, something I just remembered: newforms-admin will be a bear to merge
> > from trunk next time. There are some necessary Unicode changes in the
> > old admin that need to be p
as long as django doesn't *require* a version of python that is not on
your approved list and therefore cannot run, you shouldn't have any
problems. django is built to work on python 2.3, just because it is
also compatible with 2.4 and 2.5 shouldn't mean anything. the fact
that the code still work
indeed, many people prefer to login with their email address, or use
their email address as their username. that way they're not likely to
forget it, and can use the same one which is guaranteed not to be in
use by anyone else across all their sites. rather than having to
remember multiple usernam
