Django is not flexible

Django is not flexible at all because you can not do simple things like.


One of the most lingering criticisms of Django has been that it is not flexible. People have criticised its design as too-tightly coupled, hard to extend, and inflexible. As a result, people have recommended to roll their own using SQLchemy, Jinja or web.py.

I think this view is unfounded and wrong. You would be hard pressed to get the choices and flexibility which Django offers. Eg, while development I run with Sqlite, Dummy caching, and emails on console, while on production I switch to PostgreSQL, Memcache, and queued emails.

Many apps use this backend pattern themselves. Django registeration, Django-celery and our own merchant.

I have always been annoyed at Django is inflexible meme, and the recent Charles Leifer’s post put various Django plug points to make writing this too post easy to not do it.

Thank you for reading the Agiliq blog. This article was writen by shabda on Oct 17, 2010 in opinion .

You can subscribe ⚛ to our blog.

We love building amazing apps for web and mobile for our clients. If you are looking for developmenrt help, contact us today ✉.

Would you like to download 10+ free Django and Python books? Get them here