I'm re-writing the application in Pyramid, and so far I like it. It's a bit harder to get started and get used to though.

LOL. Which is one of the huge benefits of Django, IMHO. You can slam the speed of template rendering and the ORM all you want, but in the Django tutorial the first thing you do is use the framework to model data and display it to a user.

The Pyramid tutorial has you sending responses to the browser, which is so low-level I would hope the framework is more flexible than Django.

EDIT: While I'm responding, I'll also note that if you're running into speed issues with your templating language, you've waited too long to setup a decent caching layer. (Hello, Varnish)

I agree with the general sentiment of this comment. I strongly believe that Pyramid is a "graduation" framework.

Once one is past the honeymoon period of Django, for non-cookie cutter projects, Pyramid's very well suited for that "advanced" project where you find yourself fighting Django.

In what instances did you find yourself fighting django? I've done several huge projects in it and never had this issue.

Most of the default building blocks are very sensible and if you need to decouple them (in extreme use cases), it's not that hard.

The problem with that attitude is that when you hit the framework wall you hit it really hard.