Comments on: Pylons or Django?

By: Mark van Deursen

Mark van Deursen — Sun, 07 Mar 2010 21:23:50 +0000

We made a decision to go for Django. It’s wildly accepted, very well documented and it behaves very intuitive.

An other great advantage is the JQuery integration. (well it’s easy to be done!)

But that is only our conclusion for now. Is there someone who can change our minds?

By: Ben Bangert

Ben Bangert — Thu, 22 Oct 2009 20:31:36 +0000

Have you looked at TurboGears2? It has an admin interface, and is built on top of Pylons. There’s also Rum, which provides a db admin UI for SQLAlchemy models, FormAlchemy also quickly turns SA models into an admin tool, and there’s Sprox which is used under the hood for TG2′s admin (which should work with fairly vanilla Pylons apps soon I believe).

By: Lyndsy SImon

Lyndsy SImon — Thu, 22 Oct 2009 18:55:46 +0000

I understand where you’re coming from, but I have to disagree with your statement that “Django tries to be everything,” as I find the exact opposite to be the case.

Django is amazing for what it does, and that is help you quickly develop dynamic websites. If I have a new project, and it fits within the scope of Django’s mission, I’ll use Django every time. If I’m bolting on functionality to an existing site, the Django probably isn’t the right choice. Likewise, if I’m using data from several sources, or trying to share a DB with another app, I’m not likely to go with Django.

I’ve not used Pylons, as my first experience with Python was Django, but I’m surely looking for something more generic. As it stands, if a site doesn’t fit the mold, I’m falling back to PHP (CodeIgniter). I like Python very much, though, and I will soon get around to deciding on a more all-purpose framework. That could be Pylons, it could be TurboGears, Zope… Who knows? No matter what I chose, though, Django will still be my “go-to” tool for rapid development.