You can make a 'views' subfolder in your app folder, and make sure it
contains an __init__.py file (can be empty).
My personal opinion is that going overboard trying to make your python
file structure 'neater' will eventually bite you in the ass. It wasn't
too bad for views, but became import
There are no restrictions at all on this. Remember that the view is
called via urls.py, so you define your different views & files there.
Just a point of interest, though - models don't always match up with
views. In fact, most of my views contain at least two or three models.
Rather than break
I'd like to have a separate view files for each model just to make
everything a little neater. What's the best way to do this?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this
3 matches
Mail list logo
