It is funny you mention that.... I know I am working on open source content management platform with some other people, built on turbogears, geared specifically for web communities, like user groups etc.
We are going to launch our bleeding edge alpha version on June 14th. Our plan is exactly that....build an application on top of turbogears using best practices and lets see what happens. We are launching it to coincide with a big Google sponsored python talk in the Atlanta, GA. If your gonna be in the area, hit me up.... http://www.feestjeproject.com/ Noah Gift On 5/21/07, iain duncan <[EMAIL PROTECTED]> wrote: > > On Sun, 2007-20-05 at 21:46 +0000, AD. wrote: > > On May 20, 6:30 am, Jorge Godoy <[EMAIL PROTECTED]> wrote: > > > I'd either choose Pylons or TG. And today, it looks like TG is > > > friendlier and easier to get started. Pylons might pay in the long run > > > -- but then, you'll be able to use WSGI with TG as well and some app > > > sharing between those might be possible. > > > > That's a good point. > > > > I'm more of a lurker* than an active TG user, but TG and Pylons seem > > (from a distance at least) to be more forward looking than Django in > > terms of interoperability with other Python web apps and frameworks. > > Django while being a bit more mature as a project seems a bit more > > insular and self contained. > > > > So it seems to me that TG and Pylons aren't as reliant on a single > > development community for their long term success. There is more > > cooperation, code reuse and compatibility going on with TG and Pylons > > and their component projects which means that a smaller community can > > be just as effective as a larger community. It seems a more scalable > > community even if it does create more choices for new developers. > > > > I think the TG and (especially) Pylons communities are just at earlier > > stages of growth than Djangos, but that their design decisions are > > more sustainable (is that the right word?) for Python web development > > and will lead to more convergence and compatibility rather than > > divergence (which has hurt Python in the past I reckon), and growing > > Python web development as a whole. > > > > But hey, my slight knowledge of Django is a little out of date and > > they might be moving in that direction as well now - which would be > > even cooler for Python. Corrections welcome. > > > > * Currently doing a lot of Drupal stuff (I like Drupal but don't like > > PHP), but would love to do more Python web development and is waiting > > for a good project to come along to convince my employers... > > Very good points Anton. You pretty much summarized why I switched from > Django to TG. And I hear you on the Drupal. While hacking on Drupal is a > PITA, Drupal itself is a very nice product from a customers perspective. > I'm sure it is only a matter of time before we see TG/Pylons based > Drupals, and that will make it MUCH easier to convince clients to switch > to python! > > Iain > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
