On 8/28/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> Here's a suggestion to pull the options out of
> django.core.management.ManagementUtility: What if we just read the
> command after manage.py/django-admin.py and then passed the rest of the
> parsing to a separate execute method for each Command subclass. I'm
> envisioning something like
>
> class Command(BaseCommand):
> options = { 'option_name': dict_for_kwargs_to_add_option }
>
> In the execute method of Command, we'd build up the options for the
> particular command, including any options from superclasses (like
> --settings, which I think every command can use).
I like this! Sure, please go right ahead and give it a shot.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
