Django (web framework)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
For other uses, see Django.
Django logo.svg
The default Django page
The default Django page
Original author(s) Lawrence Journal-World
Developer(s) Django Software Foundation
Initial release 21 July 2005; 13 years ago (2005-07-21)[1]
Stable release 1.9.6[2] (May 2, 2016; 2 years ago (2016-05-02)) [±]
Preview release 1.9rc2[3] (November 24, 2015; 2 years ago (2015-11-24)) [±]
Development status Active
Written in Python
Size 6.92 MB
Type Web framework
License 3-clause BSD
Website {{#property:P856}}

Django (/ˈæŋɡ/ JANG-goh)[4] is a free and open-source web framework, written in Python, which follows the model–view–controller (MVC) architectural pattern.[5][6] It is maintained by the Django Software Foundation (DSF), an independent organization established as a 501(c)(3) non-profit.

Django's primary goal is to ease the creation of complex, database-driven websites. Django emphasizes reusability and "pluggability" of components, rapid development, and the principle of don't repeat yourself. Python is used throughout, even for settings files and data models. Django also provides an optional administrative create, read, update and delete interface that is generated dynamically through introspection and configured via admin models.

Some well-known sites that use Django include Pinterest,[7] Instagram,[8] Mozilla,[9] The Washington Times,[10] Disqus,[11] the Public Broadcasting Service,[12] and Bitbucket.[13]


Django was born in the fall of 2003, when the web programmers at the Lawrence Journal-World newspaper, Adrian Holovaty and Simon Willison, began using Python to build applications.[14] It was released publicly under a BSD license in July 2005. The framework was named after guitarist Django Reinhardt.[14]

In June 2008, it was announced that a newly formed Django Software Foundation (DSF) would maintain Django in the future.[15]



Screenshot of the Django admin interface for modifying a user account.

Despite having its own nomenclature, such as naming the callable objects generating the HTTP responses "views",[5] the core Django framework can be seen as an MVC architecture.[6] It consists of an object-relational mapper (ORM) that mediates between data models (defined as Python classes) and a relational database ("Model"); a system for processing HTTP requests with a web templating system ("View") and a regular-expression-based URL dispatcher ("Controller").

Also included in the core framework are:

  • a lightweight and standalone web server for development and testing
  • a form serialization and validation system that can translate between HTML forms and values suitable for storage in the database
  • a template system that utilizes the concept of inheritance borrowed from object-oriented programming
  • a caching framework that can use any of several cache methods
  • support for middleware classes that can intervene at various stages of request processing and carry out custom functions
  • an internal dispatcher system that allows components of an application to communicate events to each other via pre-defined signals
  • an internationalization system, including translations of Django's own components into a variety of languages
  • a serialization system that can produce and read XML and/or JSON representations of Django model instances
  • a system for extending the capabilities of the template engine
  • an interface to Python's built in unit test framework

Bundled applications

The main Django distribution also bundles a number of applications in its "contrib" package, including:


Django's configuration system allows third party code to be plugged into a regular project, provided that it follows the reusable app[18] conventions. More than 2500 packages[19] are available to extend the framework's original behavior, providing solutions to issues the original tool didn't: registration, search, API provision and consumption, CMS, etc.

This extensibility is, however, mitigated by internal components dependencies. While the Django philosophy implies loose coupling,[20] the template filters and tags assume one engine implementation, and both the auth and admin bundled applications require the use of the internal ORM. None of these filters or bundled apps are mandatory to run a Django project, but reusable apps tend to depend on them, encouraging developers to keep using the official stack in order to benefit fully from the apps ecosystem.

Server arrangements

Django can be run in conjunction with Apache, NGINX using WSGI, Gunicorn, or Cherokee using flup (a Python module).[21][22] Django also includes the ability to launch a FastCGI server, enabling use behind any web server which supports FastCGI, such as Lighttpd or Hiawatha. It is also possible to use other WSGI-compliant web servers.[23] Django officially supports four database backends: PostgreSQL, MySQL, SQLite, and Oracle. Microsoft SQL Server can be used with django-mssql on Microsoft operating systems,[24] while similarly external backends exist for IBM DB2,[25] SQL Anywhere[26] and Firebird.[27] There is a fork named django-nonrel, which supports NoSQL databases, such as MongoDB and Google App Engine's Datastore.[28]

Django may also be run in conjunction with Jython on any Java EE application server such as GlassFish or JBoss. In this case django-jython must be installed in order to provide JDBC drivers for database connectivity, which also provides functionality to compile Django in to a .war suitable for deployment.[29]

Google App Engine includes support for Django version 1.x.x[30] as one of the bundled frameworks.

Version history

Red Not supported
Yellow Still supported
Green Current version
Version Date Notes
0.90[31] 16 Nov 2005
0.91[32] 11 Jan 2006 "new-admin"
0.95[33] 29 Jul 2006 "magic removal"
0.96[34] 23 Mar 2007 "newforms", testing tools
1.0[35] 3 Sep 2008 API stability, decoupled admin, unicode
1.1[36] 29 Jul 2009 Aggregates, transaction based tests
1.2[37] 17 May 2010 Multiple db connections, CSRF, model validation
1.3[38] 23 Mar 2011 Class based views, staticfiles
1.4[39] 23 Mar 2012 Timezones, in browser testing, app templates. [40]
1.5[41] 26 Feb 2013 Python 3 Support, configurable user model
1.6[42] 6 Nov 2013 Dedicated to Malcolm Tredinnick, db transaction management, connection pooling.
1.7[43] 2 Sep 2014 Migrations, application loading and configuration.
1.8[44] 1 Apr 2015 Native support for multiple template engines. Long-term support release, supported until at least April 2018
1.9[45] 1 Dec 2015 Automatic password validation. New styling for admin interface.

Development tools with Django support

For developing a Django project, no special tools are necessary, since the source code can be edited with any conventional text editor. Nevertheless, editors specialized on computer programming can help increase the productivity of development, e.g. with features such as syntax highlighting. Since Django is written in Python, text editors which are aware of Python syntax are beneficial in this regard.

Integrated development environments (IDE) add further functionality, such as debugging, refactoring, unit testing, etc. As with plain editors, IDEs with support for Python can be beneficial. Some IDEs that are specialized on Python additionally have integrated support for Django projects, so that using such an IDE when developing a Django project can help further increase productivity. For comparison of such Python IDEs, see the main article:


There is a semiannual conference for Django developers and users, named "DjangoCon", that has been held since September 2008. DjangoCon is held annually in Europe, in May or June;[46] while another is held in the United States in September, usually in Portland, Oregon.[47] The 2012 DjangoCon took place in Washington D.C from 3 to 8 September. 2013 DjangoCon was held in Chicago at the Hyatt Regency Hotel and the post-conference Sprints were hosted at Digital Bootcamp, computer training center.[48]

Django mini-conferences were held in Hobart, Australia in July 2013 and Brisbane, Australia in August 2014.[49]

Ports to other languages

Django's template design has been ported to other languages besides Python, providing decent cross-platform support. Some of these options are more direct ports, while others are inspired by Django, retaining its concepts but taking greater liberties to deviate from Django's design.


This list is an extraction from Current Django Books

External links

See also


  1. "Django FAQ". Retrieved 2 September 2014. 
  2. Graham, Tim (2 May 2016). "Django bugfix releases issued: 1.9.6 and 1.8.13". Django Weblog. Retrieved 3 May 2016. 
  3. Graham, Tim (24 November 2015). "Security releases issued: 1.9rc2, 1.8.7, 1.7.11". Django Weblog. Retrieved 27 November 2015. 
  4. "FAQ: General - Django documentation - Django". Retrieved 30 April 2016. 
  5. 5.0 5.1 "FAQ: General - Django documentation - Django". Retrieved 30 April 2016. 
  6. 6.0 6.1 Adrian Holovaty, Jacob Kaplan-Moss; et al. The Django Book. Django follows this MVC pattern closely enough that it can be called an MVC framework 
  7. "What is the technology stack behind Pinterest?". Retrieved 30 April 2016. 
  8. "What Powers Instagram: Hundreds of Instances, Dozens of Technologies". 
  9. "Python". Mozilla Developer Network. Retrieved 30 April 2016. 
  10. Retrieved on 2014-05-30.
  11. "Scaling Django to 8 Billion Page Views". 
  12. "20 Creative Websites Running Django". 
  13. "DjangoSuccessStoryBitbucket – Django". Retrieved 30 April 2016. 
  14. 14.0 14.1 "Django's History". The Django Book. Retrieved 6 June 2013. 
  15. "Announcing the Django Software Foundation - Weblog - Django". Retrieved 30 April 2016. 
  16. "Security in Django". Django Project. Retrieved 25 March 2013. 
  17. Socol, James (2012). "Best Basic Security Practices (Especially with Django)". Retrieved 25 March 2013. 
  18. "What is a reusable app? — django-reusable-app-docs 0.1.0 documentation". Retrieved 30 April 2016. 
  19. "Django Packages". Retrieved 30 April 2016. 
  20. "Design philosophies - Django documentation - Django". Retrieved 30 April 2016. 
  21. Django documentation of deployment
  22. "Cherokee Web Server - Cookbook Setting up Django - Cherokee Documentation". Retrieved 30 April 2016. 
  23. How to use Django with Apache and mod_wsgi. Official Django documentation.
  24. "Manfre / django-mssql / source / — Bitbucket". Retrieved 30 April 2016. 
  25. ibmdb. "GitHub - ibmdb/python-ibmdb: Automatically exported from". GitHub. Retrieved 30 April 2016. 
  26. "Google Code Archive - Long-term storage for Google Code Project Hosting.". Retrieved 30 April 2016. 
  27. maxirobaina. "GitHub - maxirobaina/django-firebird: Firebird SQL backend for django". GitHub. Retrieved 30 April 2016. 
  28. "Django non-rel". Retrieved 30 April 2016. 
  29. beachmachine. "GitHub - beachmachine/django-jython: Database backends and extensions for Django development on top of Jython.". GitHub. Retrieved 30 April 2016. 
  30. Running Pure Django Projects on Google App Engine. (2010-11-01). Retrieved on 5 December 2011.
  31. "Introducing Django 0.90". Django weblog. Retrieved 2 February 2013.
  32. "Django 0.91 released". Django weblog. Retrieved 2 February 2013.
  33. "Introducing Django 0.95". Django weblog. Retrieved 2 February 2013.
  34. "Announcing Django 0.96!". Django weblog. Retrieved 2 February 2013.
  35. "Django 1.0 released!". Django weblog. Retrieved 2 February 2013.
  36. "Django 1.1 released". Django weblog. Retrieved 2 February 2013.
  37. "Django 1.2 released". Django weblog. Retrieved 2 February 2013.
  38. "Django 1.3 released". Django weblog. Retrieved 2 February 2013.
  39. "Django 1.4 released". Django weblog. Retrieved 2 February 2013.
  40. "Django’s release process - Django documentation - Django". Retrieved 30 April 2016. 
  41. "Django 1.5 released" Django weblog. Retrieved 27 February 2013.
  42. "Django 1.6 released" Django weblog. Retrieved 6 November 2013.
  43. "Django 1.7 released" Django weblog. Retrieved 4 September 2014.
  44. "Django 1.8 released" Django weblog. Retrieved 2 April 2015.
  45. "Django 1.9 released" Django weblog. Retrieved 1 December 2015.
  46. DjangoCon EU series,
  47. DjangoCon US series,
  48. "DjangoCon". DjangoCon. Retrieved 29 July 2012. 
  49. DjangoCon AU 2013. Retrieved on 2014-05-30.