FWIW, that isn't a fault of the framework per se; I have had no problems with Pylons doing something it shouldn't have done. You have to understand what the code is doing, and each framework has a different learning curve, but in my experience Pylons is as usable, expressive, and understandable as Django.
I'm certainly just a single data point. The difference between Pylons and Django could have been documentation alone, and could have been unique to me.
