On 8/15/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > 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.
I wholeheartedly agree that this functionality would be useful, but I'm not sure I like the idea of specifying a structure for it. I think I'd rather see a registration utility like the template library uses, so apps could use whatever structure they like, and just register them in management.py, since that's already used to look for syncdb handlers anyway. That's just my opinion, but it seems like it could avoid a lot of bikeshed discussions where people debate the best file structure to use. -Gul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
