3 ms·
I prefer Pylons for many reasons. One of them is that SQLAlchemy is the single most powerful SQL library I've ever used, and Pylons makes it easy to use SQLAlch
by inklesspen 19y ago
I prefer Pylons for many reasons. One of them is that SQLAlchemy is the single most powerful SQL library I've ever used, and Pylons makes it easy to use SQLAlchemy, while Django doesn't. This is just one example of Django's reluctance to use superior outside solutions.
- astrec 19y agoActually there has been a SQLAlchemy branch for over a year. Last I check it had stagnated - not enough interest.
- inklesspen 19y agoIt's a wonder why, when Django's form validation and admin panels require the Django ORM, and last I heard, using the SQLAlchemy branch required extra work.
- astrec 19y agoThe SQLAlchemy branch was intended to seamlessly integrate with the model api - in other words you needn't know it was there. I don't think it got too far. Form validation is not tied to the Django ORM.
- inklesspen 19y agoThat's funny, because when I was going through the newforms code, it had a lot of ties to the ORM.
- astrec 19y agoAnd yet form validation is not tied to the ORM. The ORM is leverage where a form is generated from a model, but that's not what you said.
- cainus 19y agoI'd have to second this. The Pylons project doesn't seem to suffer from the NIH syndrome that the django project does, and because of that, they're free to choose best-of-breed tools for every scenario. I think the fact that turbogears 2.0 is going to be based on pylons is a great win for both projects. It really gives you the feeling that if TheGreatestTemplateEngineEver or TheTransparentestORMEver gets invented tomorrow, these guys will be the first to support it. That kind of unashamed blatant code thievery deserves some respect. ;)