Django MVC pattern for non database driven models?

Your models.py can be (and sometimes is) empty. You are not obligated to have a model which maps to a database.

You should still have a models.py file, to make Django's admin happy. The models.py file name is important, and it's easier to have an empty file than to try and change the file expected by various admin commands.

The "model" -- in general -- does not have to map to a database. The "model" -- as a general component of MVC design -- can be anything.

You can -- and often do -- define your own "model" module that your views use. Just don't call it models.py because it will confuse Django admin. Call it something meaningful to your application: foo.py. This foo.py manipulates the real things that underpin your application -- not necessarily a Django Model.model subclass.

Django MVC does not require a database mapping. It does explicitly expect that the module named models.py has a database mapping in it. So, use an empty models.py if you have no actual database mapping.

Your views.py can use

import foodef index( request ):    objects = foo.somelistofobjects()    *etc.*

Django allows you to easily work with no database mapping. Your model can easily be anything. Just don't call it models.py.

Edit.

Are Views registered with Models? No.

On update to the Model by the Controller the Views get notified? No.

Is the Model strictly the data respresentation as this is really MVP? Yes.

Read the Django docs. It's simple.

Web Request -> URL mapping -> View function -> Template -> Response.

The model can be used by the view function. The model can be a database mapping, or it can be any other thing.