i see. I created a admin.py in my app and added a "import admin" to __init__.py. In the admin.py I had to import all from the models.py.
Tested it and it works. Does that sound right? -al On Apr 30, 3:22 pm, Rajesh Dhawan <[EMAIL PROTECTED]> wrote: > On Apr 30, 4:39 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > As per the NewFormsAdmin Branch > > -http://code.djangoproject.com/wiki/NewformsAdminBranch > > - there is a proposal convention that reads as follows: > > > """A proposal convention: Specifying all admin options in a file > > called admin.py, and import it in the __init__.py file of your > > application module to do the registering during the initialization.""" > > > It seems that this proposed conversion is not in place yet. > > Nothing stops you from using that convention, actually. Have you tried > it? > > > If not, > > what should the current best practice way to do this be? Place the > > admin code in the model.py with the actual model classes? Or maybe > > place the admin code in a admin.py and call it from within model.py or > > something. (Model and Admin code together in one file becomes a bit of > > a mess.) > > That's why the recommendation above is to separate your admin code out > in to admin.py. > > -Rajesh D --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
