Django has a better administrative interface (equivalent to our addadmin) bot nothing equivalent web2py admin. Django has no migrations. Every time you update the models you have to alter tables yourself. There may be third party packages that do mirations but are not in the stable branch.
Django runs on GAE but, if you use the Django modules provided by google, you have to rewrite queries using the google APIs because the official Django ORM does not support GAE. There is a patch to support GAE but it is not in stable. Anyway, it does not support it as seamlessly as the web2py dal does. Django is more verbose by at least a factor 2. Django uses a different language for templates that is not python. It is not even Turing complete therefore it limits very much what you can do. In shops where you have designers and you want to limit how much damage their bugs can make, that is a plus (Django users make this point). My experience is that good designers can program and you do not want to restrict them to much. Certain queries in Django are easier (in particular involving simple many-to-many) but web2py has more flexibility (queries with aggregates, left joins and nested selects) because web2py's DAL is closer to SQL than Django's ORM. I believe we have a more friendly community but that you can judge for yourself. On Feb 6, 9:36 am, Luther Goh Lu Feng <elf...@yahoo.com> wrote: > Hi all, > > I am about to have a constructive discussion about web2py vs django > with a team member of mine before we decide whether to implement a > project. He is an expert with django while I consider myself an > intermediate web2py user. > > This is not a flamebait, but I would like to mainly hear pain points > about web2py and django, so that we can make a good decision. I am > only familiar with web2py, and only brushed the surface of django. > > Thanks in advance.
