Organization code django project, linking applications

Nice app django — uniswa, does one thing, does it well, has some external API to communicate with other modules. Usually, even in a small project there are about a dozen apps. The advantages of this approach — much easier to test, reuse of code, can be relatively painless to change the implementation of a module without disrupting the entire site.
\r
Anti-pattern — a monolithic application (usually just one or two). Them, among other things, harder to maintain, because the code performs many not directly connected tasks (functions responsible for the generation of RSS and changing user avatars, are close together in this file, nothing will be done without a pint and ctrl-F). This is especially true when the team added new developer.
\r
Application interaction — a much more extensive topic, it so easily in two sentences, not to disclose, I think.

I have not much experience with Django, but I think this is the method of crushing, and uses a separate app for every task.
And what about interaction — so that is in Python is a very flexible system imports, no?

I have a big old app to Django. Use the balance between these two approaches: most of the functionality in one big application that is split in packages of modules, such as:
— big_app
— models
— profile.py
— content.py
— events.py
— forum.py
— views
— forum.py
— event.py
\r
Part in a separate app, I don't know why, because they still may not be reused, as too tied to the specifics of the application and use of imports from the main application. But I didn't make this structure. I would probably instead would add modules to the existing large application and a separate application would only code that can be reused (so we have a little, but there).