Hi, DavidG wrote: > 1. ease/speed of programming > I think WSGI-nature of Pylons makes it very good balanced choice between Django and Zope. Easy to learn as Django and easy to extend as Zope. > 2. ease of testing > Nothing different than in other Python web frameworks. > 3. scalability > I have not developed anything that big yet. I believe it scales well. As far as I know about sites running Pylons the biggest one might be http://widgets.opera.com/ and that site has a lot of users. http://files.myopera.com/Sharebear/EuroPython08/SpringIntoPylons/index.html > 4. reliability > You can reach desired level or reliability by combining pip, virtualenv and wsgi components. > 5. maintainability > That's more about how you work not about frameworks. > 6. flexibility > If you don't like one WSGI component you can write your own. Most probably you will not need to do that but I did that once (because of OpenID). > 7. availability of good libraries > I believe there is no problem here.
Regards, Dalius --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
