[ergo14]

How about you read that again, I think you misunderstood my point - or I was uncler, since english is not my native language. And i'm the OP in case you didn't notice that;-)

"I'm curious why you think Django lacks quality and maturity." - This is what he wrote, so i gave him main reason why django is not the tool for me.

Which are perfectly valid in my opinion. And no - with sqlalchemys design, it DOES NOT require you to change your code if you just need to use few models with other databases - the change was about 20 lines of code in my case. Which i take would be not possible at all with django 1.0. You are right about "right tool for the job", for the kind of work I do, glue frameworks like pylons or bfg are a lot better choice - it's really way harder to corner me with some requirement that this stack can't handle.

And as for challenges, like I said - business conditions changed and I had to connect to 3 db's at once, no problems at all - if one chooses his tools very carefully in advance that can save a lot of headache later. Like I said, sorry for confusing you.

You can't predict everything that client could need/forgot to mention, so the more versatile your toolbox is the better.