> Django doesn't allow clean separation between business logic and presentation logic, forcing both into its "views". Rails does. Django isn't a traditional "M

> Django doesn't allow clean separation between business logic and presentation logic, forcing both into its "views". Rails does. Django isn't a traditional "MVC," so "views" in Django have a different meaning. In all reality a Django "view" is the "C" in "MVC," and the template is the "V." I'm afraid I fail to see that point. I also fail to see your point about SVN+QuerySetRefactor... as I've never used either branch and have gotten everything done that I've needed to. There will come a time when that stuff gets merged back into trunk and I'll have to do some conversion, but traditionally it has been very minimal (see: old school MagicRemovalBranch).