Differences between Django and Pyramid routing

Posted: [Source]
Tags:  django pyramid python routing

Recently I had a chance to familiarize myself with django framework. Having some experience with Pyramid (with SQLAlchemy), I can't stop myself comparing these two frameworks. The first big difference, which struck me, was routing.

While pyramid's routing is marvellously flexible, django is somewhat limited. Even though it utilises regular expression for route patterns, it looks more crude, than what's pyramid offering. I'm aware, that I'm not familiar with everything in django yet, but that's my first impression.

Drawback for me is also having one route per action. I used pyramid view_onfig's predicates in pyramid quite extensively, so, whenever I had chance, I had three action to serve one entity (simplest way in edit: GET request had it's own action, and POST was the other, all on one route).

The route predicates was another great thing behind pyramid routing. Route pattern were rather simple, but predicates are what makes this routing system great. I could check if I had slug/id even before I got to the view, no need to throw 404 exception in the view in case entity does not exists... And while we're at it, pregenerators. I could have whatever route params defined, and pass objeck as user, and just remap object into parameters in pregenerator.

The pregenerator is still far in case of ease of use behind symfony 1.4, where such pregenerator action would be just a routing config, but still, way better than what I see in django, at least at the moment.

Some reading:

Comments powered by Disqus