I`ve asked for almost the exact same thing some time ago, but the answer was that normal python knowledge regarding modules and packages should help you organize your project.
For example, instead of having several models in one models.py file, you can create a folder in your app-folder called models, put each model in a seperate <modelname>.py-file, put a __init__.py in the folder which imports all your model-files ( and probably remove the old models.py). Then you can still do from appname.models import *, but the files containing your model are smaller and easier to navigate. Don`t know it it helps you much.I still would like to see more documentation and examples on how to manage big project with large models. Regards, Thomas On Thu, Jan 13, 2011 at 1:45 PM, Олег Корсак <kamikaze.is.waiting....@gmail.com> wrote: > hello. My models.py file became very big and actually I can divide that > app for 2-3 different apps. But the problem is that almost all models > are related to one model which is common and will be in different app. > Is it still a good idea to divide into different apps and make import > from external app? > > Thanks > > -- Mvh/Best regards, Thomas Weholt http://www.weholt.org -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
