On 8/15/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> I'd like to split this into several files, turning
> django.core.management into a package. The purest way of splitting the
> functionality would be to give each manage.py action ("runserver",
> "syncdb", etc.) its own Python module, like this:
Sounds like a really good idea to me -- looking forward to it!
I'd like to suggest a (somewhat controversial) extension:
Let any (installed) app provide its own manage.py actions in a similar
way -- something like::
schema_evolution/
management/
__init__.py
commands/
__init__.py
evolve.py
This would let projects like S-E -- there's a reason I used it for the
example -- provide custom management actions; installing said app
would make those actions "appear" in manage.py. This would go a long
way towards letting optional bits "feel" more built-in.
Jacob
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
