|Original author(s)||Adrian Holovaty, Simon Willison|
|Developer(s)||Django Software Foundation|
|Initial release||21 July 2005|
3.2.5 / 1 July 2021
Django ( JANG-goh; sometimes stylized as django) is a Python-based free and open-source web framework that follows the model-template-views (MTV) architectural pattern. It is maintained by the Django Software Foundation (DSF), an American independent organization established as a 501(c)(3) non-profit.
Django's primary goal is to ease the creation of complex, database-driven websites. The framework emphasizes reusability and "pluggability" of components, less code, low coupling, 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.
Django was created 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. Jacob Kaplan-Moss was hired early in Django's development shortly before Simon Willison's internship ended. It was released publicly under a BSD license in July 2005. The framework was named after guitarist Django Reinhardt. Adrian Holovaty is a Romani jazz guitar player and a big fan of Django Reinhardt.
Despite having its own nomenclature, such as naming the callable objects generating the HTTP responses "views", the core Django framework can be seen as an MVC architecture. 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:
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 conventions. More than 2500 packages are available to extend the framework's original behavior, providing solutions to issues the original tool didn't tackle: registration, search, API provision and consumption, CMS, etc.
This extensibility is, however, mitigated by internal components' dependencies. While the Django philosophy implies loose coupling, 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.
Django can be run in conjunction with Apache, Nginx using WSGI, Gunicorn, or Cherokee using flup (a Python module). 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. Django officially supports five database backends: PostgreSQL, MySQL, MariaDB, SQLite, and Oracle. Microsoft SQL Server can be used with django-mssql on Microsoft operating systems, while similarly external backends exist for IBM Db2, SQL Anywhere and Firebird. There is a fork named django-nonrel, which supports NoSQL databases, such as MongoDB and Google App Engine's Datastore.
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 can provide functionality to compile Django in to a .war suitable for deployment.
The Django team will occasionally designate certain releases to be "long-term support" (LTS) releases. LTS releases will get security and data loss fixes applied for a guaranteed period of time, typically 3+ years, regardless of the pace of releases afterwards.
|Old version, no longer maintained: 0.90||16 Nov 2005|
|Old version, no longer maintained: 0.91||11 Jan 2006||"new-admin"|
|Old version, no longer maintained: 0.95||29 Jul 2006||"magic removal"|
|Old version, no longer maintained: 0.96||23 Mar 2007||"newforms", testing tools|
|Old version, no longer maintained: 1.0||3 Sep 2008||API stability, decoupled admin, unicode|
|Old version, no longer maintained: 1.1||29 Jul 2009||Aggregates, transaction based tests|
|Old version, no longer maintained: 1.2||17 May 2010||Multiple db connections, CSRF, model validation|
|Old version, no longer maintained: 1.3||23 Mar 2011||Class based views, staticfiles|
|Old version, no longer maintained: 1.4 LTS||23 Mar 2012||Time zones, in browser testing, app templates.|
|Old version, no longer maintained: 1.5||26 Feb 2013||Python 3 Support, configurable user model|
|Old version, no longer maintained: 1.6||6 Nov 2013||Dedicated to Malcolm Tredinnick, db transaction management, connection pooling.|
|Old version, no longer maintained: 1.7||2 Sep 2014||Migrations, application loading and configuration.|
|Old version, no longer maintained: 1.8 LTS||1 Apr 2015||Native support for multiple template engines. Support ended on 1 April 2018|
|Old version, no longer maintained: 1.9||1 Dec 2015||Automatic password validation. New styling for admin interface.|
|Old version, no longer maintained: 1.10||1 Aug 2016||Full text search for PostgreSQL. New-style middleware.|
|Old version, no longer maintained: 1.11 LTS||4 Apr 2017||Last version to support Python 2.7. Support ended on 1 April 2020|
|Old version, no longer maintained: 2.0||2 Dec 2017||First Python 3-only release, Simplified URL routing syntax, Mobile friendly admin.|
|Old version, no longer maintained: 2.1||1 Aug 2018||Model "view" permission.|
|Older version, yet still maintained: 2.2 LTS||1 Apr 2019||Security release. Supported until at least April 2022|
|Older version, yet still maintained: 3.0||2 Dec 2019||ASGI support|
|Older version, yet still maintained: 3.1||4 Aug 2020||Asynchronous views and middleware|
|Current stable version: 3.2 LTS||6 Apr 2021||Extended Support until at least April 2024|
|Future release: 4.0||Dec 2021||Extended Support until at least April 2023|
|Future release: 4.1||Aug 2022||Extended Support until at least December 2023|
|Future release: 4.2 LTS||April 2023||Extended Support until at least April 2026|
|Future release: 5.0||December 2023||Extended Support until at least April 2025|
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, and unit testing. 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; while another is held in the United States in August or September, in various cities. 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. The 2014 DjangoCon US returned to Portland, OR from 30 August to 6 September. The 2015 DjangoCon US was held in Austin, TX from 6 to 11 September at the AT&T Executive Center. The 2016 DjangoCon US was held in Philadelphia, PA at The Wharton School of the University of Pennsylvania from 17 to 22 July. The 2017 DjangoCon US was held in Spokane, WA; in 2018 DjangoCon US was held in San Diego, CA. DjangoCon US 2019 was held again in San Diego, CA from Sept 22-27.
Programmers have ported Django's template engine design from Python to other languages, providing decent cross-platform support. Some of these options are more direct ports; others, though inspired by Django and retaining its concepts, take the liberty to deviate from Django's design:
Django as framework is capable of building a CMS. However, there are a few CMSs already available which are built upon Django. Below is list of few of the CMSs built upon Django framework:
Django follows this MVC pattern closely enough that it can be called an MVC framework
This list is an extraction from Current Django Books