I've noticed that there have been a lot of things in common: Web2py _didn't_ have very good docs, at least relative to Django's (which are spectacular), but now that the Web2py book is available online, that issue is kind of moot.
Admin -- Web2py has two different Admins, one which doesn't have a Django equivalent (lets you manage apps, etc. from it, pretty handy) and a not-as-good-as-Django's-Admin appadmin. Although it certainly could do the job for my tiny site =) And the explicit vs. implicit imports: Personally, I love the fact that the request object is available all over the place, including models, and that I don't have to do any importing. My final complaint about Web2py is its templating engine: if I want my Dad to do the HTML on my website, I'd rather not make him learn "Python", per se, rather, I'd like him to learn a slightly different but less strict of a syntax templating engine. Ok, I'm done. Feel free to comment on anything above (including you Massimo =) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
