Thanks for the links, I was sure someone had done this before. Looks like they're scanning the models.py source code and finding the information there. I think it would be easier and cleaner to generate it dynamically.
@oggie rob, @russ magee Yep, it would only ever be needed once, and cluttering the management is not the best idea. In any case, it would be added to django.contrib.admin.management, but the effect is the same. Maybe some people might think its global usefulness overcomes its contribution to clutter. Also, I wasn't thinking of a complete conversion tool, just something to get people started, as simple as possible. What people do with the results is up to them, the file just gets generated, porting the old commands to the new one and they are free to edit it how they wish. I'll write it up quickly, as it doesn't seem to be too difficult at all and see what everyone thinks. Cheers, -- Will Hardy w: http://www.willhardy.com.au --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
