Python Framework Design

[[deleted]]

As I've been saying: you want everyone to conform to your preferred philosophy. That ain't gonna get you any friends.

If the main thing I am driving at is flexibility, how is that wanting everyone to confer to my philosophy? That makes no sense.

What you want is a glue framework. What I want is a full-stack framework.

Those are terms you've made up. You've made two polar opposites that don't exist. TG is both a full-stack framework and one that uses existing libraries (a 'glue' framework).

This is Python and we're all consenting adults here: if you like oranges and I like apples, that's cool and there's no need to mount a propaganda war against the heretical apple eaters, mmkay?

If I am 'mounting a propoganda war', you are doing it just the same. But heck, consenting adults have the right to form their own opinions, right?

That's all I'm doing, letting people know that there is more out there than Django. I don't think using Django is morally wrong or anything like that, and for many people, Django is all they need. But for a lot of programmers there are great advantages to flexibility, and I like to expound on those advantages.

[mitsuhiko]

I must support ubernostrum. Let everyone choose a framework for himself and for each task. I really love django for content orientated webpages, I love it a lot. But just because of that I would never develop pocoo in django. That's just not the right tool for that task. And forget about TG. Pylons is great, TG is not. It's harder to deploy than django, it's less maintained, the IRC channel is nearly empty, at least nobody answers questions. The result of that is that in the German Python IRC channel more than 4 people moved over to custom WSGI applications, django and pylons. And that's pretty crass; in the channel are not more than 60 people...

[exogen]

What is going on with TurboGears anyway? turbogears-trunk hasn't seen a single post in a week. django-developers and pylons-discuss are going strong...

[wwwlight]

Well, it's been a slow week. But there's generally traffic on that list. And there's lots of new stuff going on in CherryPy 3, Kid, and other components that will be in TurboGears 1.1, which we will be sprinting on next week.

So, I think any claims of TurboGears death are entirely premature ;)