[BangPypers] Evaluating Web Frameworks based on certain criteria

[Gopalakrishnan Subramani]

I was using Pylons for nearly 3 years and moved to Flask instead of Django.
The decision is based on my  'opinion' on opinionated frameworks.

Pylons and Pyramid is completely running DIY philosophy, it was not really
fun for me (personal preference matter, no argument please). I need to look
around too many things to fix the issues or add new auth system or
framework to it.

I certainly liked Flask in that manner. It is simple and easy.

I code Python from 11:00 PM to 3:00 AM after my day job, so I tend to go
simple one than the Pyramid.

I use SqlAlchemy, Jinja2 along with Flask. With Pylons, I have used Mako
and Sql Alchemy.





On Tue, Apr 2, 2013 at 1:32 PM, Abdul Muneer <abdulmuneer at gmail.com> wrote:

> Thank you all, especially larry. Pyramid and Django are what I have looked
> at. I have worked with Django and all pylons stuff along with SQLA was
> initially cumbersome. I would have really loved to go with Django as it is
> 'easy', but there are reasons why Pyramid is built the way it is and I
> wanted to consider those factors too. I appreciate SQLA very much now,
> although I haven't encountered a scenario where I had been at a loss if I
> didn't use it.
>
> I am looking forward to experiences from people which led them towards or
> away from any framework. Did anyone hit the wall by using Django ORM? Or
> did anyone find the SQLA too heavy and needless? I certainly hit the wall
> with old pylons, or more precisely with the plugins for pylons. All those
> deprecated dependencies make the upgrade or maintenance extremely difficult
> and unreliable.
>
> Regards,
> Abdul Muneer
>
> --
> Follow me on Twitter: @abdulmuneer <http://twitter.com/#%21/abdulmuneer>
>
>
> On Tue, Apr 2, 2013 at 12:34 AM, <larryt at winfirst.com> wrote:
>
> >
> > >Hi,
> > >I need to decide on a python web-framework based on the below listed
> > >criteria.
> > >
> > >   1. Ease of customization of bundled packages
> > >   2. Ease of development
> > >   3. Long term support of frameworks
> > >   4. Learning curve
> > >   5. Logging and monitoring
> > >   6. Clustering
> > >   7. Ease of deployment
> > >   8. Testing: unit testing libraries
> > >   9. DB management
> > >   10. User management: e.g. should be possible to tie one user id to
> > >   multiple entities
> > >   11. LDAP integration
> > >
> > >What would you recommend? Please share your experiences and insights
> > >related to any of these points. Ignore the points in the list that
> appear
> > >vague to you.
> > >
> > >The existing app is written in pylons 0.9 , but as we want to enhance
> and
> > >add lot more features, we would like to rebuild it on a new framework
> > >altogether.
> > >
> > >The current web app had too many dependencies and the new versions of
> some
> > >of these libraries have conflicting requirements. Some other libraries
> > were
> > >long dead. So the choice is to rebuild entire stuff on a framework where
> > we
> > >will not end up in the same situation.
> >
> > There are probably three to look at in following the advice you've
> already
> > received: Pyramid, Django and Flask.  If you're a PC/Mac shop look first
> > and harder at Django.  Otherwise start with Flask and Pyramid.  I use
> Flask
> > because the ecosystem seems more manageable to me, but I'm sure that's
> just
> > because of my previous experience, so yours may lead you to Pyramid,
> > especially coming from pylons.
> >
> > -larry
> >
> >
> > _______________________________________________
> > BangPypers mailing list
> > BangPypers at python.org
> > http://mail.python.org/mailman/listinfo/bangpypers
> >
> _______________________________________________
> BangPypers mailing list
> BangPypers at python.org
> http://mail.python.org/mailman/listinfo/bangpypers
>