While looking at #5614[1] and thinking about fixing up the patch so it could be committed, it occurred to me that, with the infrastructure we now have for custom management commands, there's no real need for contrib/auth/create_superuser.py to exist anymore.
So what I'd *like* to do is: 1. Add a method 'create_superuser()' to UserManager, which takes username, email and password and creates a new User with 'is_staff', 'is_active' and 'is_superuser' set to True. 2. Reimplement the current create_superuser.py as a custom management action which passes through to (the newly-added) User.objects.create_superuser(). 3. Rework the install-time handler in the current contrib/auth/management.py to make use of the above. This will be the tricky bit, I imagine. Anyone have strong feelings one way or another? [1] http://code.djangoproject.com/ticket/5614 -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
