I flirted with Web2py for a while, but came back to Django. Web2py has some compelling features, including:
* ORM supports Google App Engine (with limitations of course). * Distributions can include binary executables for the core pieces (for mac and windows). * Built in server has a console for starting and stopping. * Development can be totally through the web or using traditional editors. * Applications can be packaged with one click into a tar, and installed with one click from a local tar or an URL pointing to the tar. * Many migrations, like adding a column, are automatic. (Really good for development, questionable for production). * Cherrypy server good enough for small production sites, but adaptable to other servers. I think Massimo Di Pierro has done an exemplary job with the platform. But for everything it does, it just doesn't feel as complete as Django (sorry I can't totally quantify). The documentation lags the changes - the pdf book is quickly becoming outdated. Some of the really nice features from addons called T2 and T3 were being merged into the main product, and it was hard to tell what was what. At least that was the state a couple of months ago. Django suffered some of these kinds of growing pains too, but has stabilized ans is now one of the best organized and managed multi- contributor projects I've witnessed. Often overlooked things like the *versioned* Sphinx based docs are incredibly useful, as are the several books on Django. There is one other specific "feature" of Web2Py that bothers me. There is commitment to not breaking backward compatibility - which sounds noble but can really limit refactoring and result in a fractured framework over time. HTH, Greg On Apr 22, 12:46 pm, Stef Mientki <stef.mien...@gmail.com> wrote: > Vishwajeet wrote: > > Hi All, > > > This is not to flame any war; I just wanted to know the key features > > to consider among the two web frame works. > > > What advantage and disadvantages you have when you decide using any > > one of them. > > > Thanks for your help > > I'm struggling with the same question for about 2 months now. > It seems that a lot of people who answered this question, > all have a lot of apriori knowledge of webdesign. > Questions in my opinion are never stupid, only answers can be. > > Knowing nothing about web design, this seems a very legal question to me. > With Python you can do everything, so why do you need Django or Web2Py > at all ? > > One of the selection criteria I often use, > is the support offered in discussion lists.... > ... and until now I didn't encounter the kind of answers in the web2py > list as I've seen here on this question. > > just my 2 cents as another still seeking for the right answers person, > cheers, > Stef Mientki --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
