Turbogear developers works with Pyramid guys, but no outcome is planned so far. They might create a framework on top of pyramid or do contribution to plug-ins.. If you are starter, I would advise you go with Django. Pyramid is nice for hard-core developer, when it comes to end level framework users, it still lacks of examples/tutorials, cookbooks, patterns.
I use Pyramid because of Mako and SqlAlchemy. But I have a lot of frustration when I started with Pylons 2 years back. Advantages with Django: 1. Huge community members than Pyramid/Pylons 2. There are a lot of plug-ins/todos/guides/helps/blogs available 3. There are many open-source applications to learn from 4. There are forum/blog/cms systems Django is self contained solution, where it has ORM/Templates/Views/Routing tightly couples, IMHO. Where as in Pyramid, you have Options.. Regards, Gopalakrishnan Subramani On Thu, May 19, 2011 at 7:03 PM, Dhananjay Nene <dhananjay.n...@gmail.com>wrote: > On Thu, May 5, 2011 at 3:47 PM, OOMMEN KM <oomme...@gmail.com> wrote: > > > Hi All, > > > > I would like to know which technology should I use for developing a web > > based application. > > The application will have to handle a huge amount of data and we are > using > > MySQL. > > Will mod_python a good option for the development of this application? Or > I > > need to choose some frame works? > > > > Please help me. > > > > I cannot speak for whether mod_python is dead or alive. Resolving the > Schrödinger's cat paradox could perhaps be easier. My opinions however > would > be that it would depend very substantially upon the nature of the > application. > > a. For extremely high concurrency I would look at tornado. However it has > relatively limited features - so more often than not I would usually give > it > a pass. > b. For most apps, and especially if I wanted a comprehensive well > integrated > framework - I would look to django. It also happens to perhaps be one of > the > most frequently used. > c. I chose pylons since it better followed my preference of integrating > multiple tightly focused frameworks (for templating / databases etc.). Note > that pylons is now no longer actively developed and its successor is > pyramid. However I haven't really looked at pyramid though thats the one > you > would want to look at. One particular aspect of pylons is that it does not > itself contain a ORM and is usually used with sqlalchemy. Since you > specifically mentioned large data - this option of pyramid + sqlalchemy > might give you better mileage if the huge data needs to be maintained in a > RDBMS. > > There are a number of other useful frameworks as well including web.py, > turbogears etc, but I am not experienced enough to comment on them. > > Also there are many other light weight / micro frameworks (eg. flask, > bottle > etc.) You could also consider using sqlalchemy in conjunction with such > micro frameworks as well if you need a simple web tier with some complex > database handling. > > Dhananjay > > Oommen Mathew | +91 9446917322 > > _______________________________________________ > > BangPypers mailing list > > BangPypers@python.org > > http://mail.python.org/mailman/listinfo/bangpypers > > > > > > -- > > ----------------------------------------------------------------------------------- > http://blog.dhananjaynene.com twitter: @dnene > _______________________________________________ > BangPypers mailing list > BangPypers@python.org > http://mail.python.org/mailman/listinfo/bangpypers > _______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
