On 1/20/07, Karl Guertin <[EMAIL PROTECTED]> wrote:
>
> On 1/20/07, Randall <[EMAIL PROTECTED]> wrote:
> > It's nice to see TurboGears finally pass the 1.0 milestone.  About the
> > same time TurboGears started gathering steam, several other frameworks
> > either started up or came to my attention in what looked like a Python
> > web framework revolution.
>
> It pretty much was.
>
>
> > Looks like Django and Pylons (two that I've evaluated) are moving
> > along and nearing 1.0 status.  Anyone have enough experience with these
> > other frameworks to say how they compare to TurboGears today?
>
> I use Django when I can do a project using only admin. I prefer
> SQLAlchemy, Genshi, and TG's returning dictionaries to the Django
> equivalents, so I don't use it otherwise. Pylons is recommended if you
> feel that TurboGears makes too many component choices you disagree
> with. Django has better docs than TG, TG has better docs than Pylons
> (last I checked).

Pylons and TurboGears are practically the same thing if you're using
SQLAlchemy, since none of the TG admin tools really do you any good in
that case.

The internals to Pylons make more sense to me because it's based on
lighter weight stuff than CherryPy (paste and WSGI). It's also a
breeze to debug with EvalException. Pylons pretty much covers all of
the functionality I was looking for, in a more straightforward manner
than TG... but the TG community has a lot more momentum. It would
certainly be interesting to see more cooperation between the two, e.g.
if the TG admin tools were WSGI based then it could be interchangeable
just like the Buffet template plugins that both frameworks use now.

-bob

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to