Fiddling with Django
Its been a few weeks playing with Django trunk. And a two more weeks than that, with Python. Initially, I was getting annoyed with the 'self'ishness of python. But got used to it. Python is refreshingly more powerful than Ruby,the only other dynamic language I know, IMHO. I won't go in to details of how, as this post is about Django.
These are a few things I've started liking about Django:
Also, I played a bit with django.contrib.search and PyLucene. django.contrib.search did not work out of the box, and I had to tweak it a bit. It did not support traversing Many-to-many relations for indexing and I added some crude support for that as well. I will publish the tweaks after adding full-fledged support for traversing relationships.
Its been a few weeks playing with Django trunk. And a two more weeks than that, with Python. Initially, I was getting annoyed with the 'self'ishness of python. But got used to it. Python is refreshingly more powerful than Ruby,the only other dynamic language I know, IMHO. I won't go in to details of how, as this post is about Django.
These are a few things I've started liking about Django:
- Database is driven by model classes, not the other way
- The admin application(a.k.a CRUD on steroids) for free
- Reasonably good template infrastructure
- Reasonably good testing infrastructure (the client class)
- No support for incremental model changes (syncdb cannot update existing tables!)
- No fixtures yet(okay, i don't want to write SQL scripts for fixtures now)
Also, I played a bit with django.contrib.search and PyLucene. django.contrib.search did not work out of the box, and I had to tweak it a bit. It did not support traversing Many-to-many relations for indexing and I added some crude support for that as well. I will publish the tweaks after adding full-fledged support for traversing relationships.
Labels: django, pylucene, python, rails, ruby, web application
