Are there any best practices documents to organizing large Django
projects?

Should the view code be in a file called views.py?  It seems like this
file could get rather large and hard to manage, is there some
suggested way to break it up?

Should the files with views even be called views.py, or should the
filename indicate the functionality of the view? If so, I find it hard
to manage a bunch of views.py files in ide's that have tabs of open
files where all I see is the file name. Is there some way around this?



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to