Django (web framework)
Python web framework From Wikipedia, the free encyclopedia
Django (/ˈdʒæŋɡoʊ/ JANG-goh; sometimes stylized as django)[5] is a free and open-source, Python-based web framework that runs on a web server. It follows the model–template–views (MTV) architectural pattern.[6][7] It is maintained by the Django Software Foundation (DSF), an independent organization established in the US as a 501(c)(3) non-profit.
![]() | |||
![]() | |||
Original author(s) | Adrian Holovaty, Simon Willison | ||
---|---|---|---|
Developer(s) | Django Software Foundation[1] | ||
Initial release | 21 July 2005[2] | ||
Stable release |
| ||
Repository | |||
Written in | Python[1] | ||
Type | Web framework[1] | ||
License | 3-clause BSD[4] | ||
Website | www |
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.[8] 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 Instagram,[9] Mozilla,[10] Disqus,[11] Bitbucket,[12] Nextdoor,[13] and Clubhouse.[14]
History
Django was created in the autumn 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 Willison's internship ended.[15] It was released publicly under a BSD license in July 2005. The framework was named after guitarist Django Reinhardt.[16] Holovaty is a Romani jazz guitar player inspired in part by Reinhardt's music.[17]
In June 2008, it was announced that a newly formed Django Software Foundation (DSF) would maintain Django in the future.[18]
Features
Summarize
Perspective
Components

Despite having its own nomenclature, such as naming the callable objects generating the HTTP responses "views",[6] the core Django framework can be seen as an MVC architecture.[7] 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:
- an extensible authentication system
- the dynamic administrative interface
- tools for generating RSS and Atom syndication feeds
- a "Sites" framework that allows one Django installation to run multiple websites, each with their own content and applications
- tools for generating Sitemaps
- built-in mitigation for cross-site request forgery, cross-site scripting, SQL injection, password cracking and other typical web attacks, most of them turned on by default[19][20]
- a framework for creating geographic information system (GIS) applications
Extensibility
Django's configuration system allows third party code to be plugged into a regular project, provided that it follows the reusable app[21] conventions. More than 5000 packages[22] 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,[23] 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 on ASGI or WSGI-compliant web servers.[24] Django officially supports five database backends: PostgreSQL, MySQL, MariaDB, SQLite, and Oracle.[25] Microsoft SQL Server can be used with mssql-django.
Version history
The Django team will occasionally designate certain releases to be "long-term support" (LTS) releases.[26] 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.
Version | Release date[27] | End of mainstream support | End of extended support | Notes[28] |
---|---|---|---|---|
[29] | 0.9016 Nov 2005 | |||
[30] | 0.9111 Jan 2006 | "new-admin" | ||
[31] | 0.9529 Jul 2006 | "magic removal" | ||
[32] | 0.9623 Mar 2007 | "newforms", testing tools | ||
[33] | 1.03 Sep 2008 | API stability, decoupled admin, unicode | ||
[34] | 1.129 Jul 2009 | Aggregates, transaction based tests | ||
[35] | 1.217 May 2010 | Multiple db connections, CSRF, model validation | ||
[36] | 1.323 Mar 2011 | 23 Mar 2012 | 26 Feb 2013 | Class based views, staticfiles |
[37] | 1.4 LTS23 Mar 2012 | 26 Feb 2013 | 1 Oct 2015 | Time zones, in browser testing, app templates. |
[38] | 1.526 Feb 2013 | 6 Nov 2013 | 2 Sep 2014 | Python 3 Support, configurable user model |
[39] | 1.66 Nov 2013 | 2 Sep 2014 | 1 Apr 2015 | Dedicated to Malcolm Tredinnick, db transaction management, connection pooling. |
[40] | 1.72 Sep 2014 | 1 Apr 2015 | 1 Dec 2015 | Migrations, application loading and configuration. |
[41] | 1.8 LTS1 Apr 2015 | 1 Dec 2015 | 1 Apr 2018 | Native support for multiple template engines. Support ended on 1 April 2018 |
[42] | 1.91 Dec 2015 | 1 Aug 2016 | 4 Apr 2017 | Automatic password validation. New styling for admin interface. |
[43] | 1.101 Aug 2016 | 4 Apr 2017 | 2 Dec 2017 | Full text search for PostgreSQL. New-style middleware. |
[44] | 1.11 LTS4 Apr 2017 | 2 Dec 2017 | 1 Apr 2020 | Last version to support Python 2.7. Support ended on 1 April 2020 |
[45] | 2.02 Dec 2017 | 1 Aug 2018 | 1 Apr 2019 | First Python 3-only release, Simplified URL routing syntax, Mobile friendly admin. |
[46] | 2.11 Aug 2018 | 1 Apr 2019 | 2 Dec 2019 | Model "view" permission. |
[47] | 2.2 LTS1 Apr 2019 | 2 Dec 2019 | 11 Apr 2022 | Security release. |
[48] | 3.02 Dec 2019 | 3 Aug 2020 | 6 Apr 2020 | ASGI support |
[49] | 3.14 Aug 2020 | 6 Apr 2020 | 7 Dec 2021 | Asynchronous views and middleware |
[50] | 3.2 LTS6 Apr 2021 | 7 Dec 2021 | April 2024 | Tracking many to many relationships, added support for Python 3.11 |
[51] | 4.07 Dec 2021 | 3 Aug 2022 | April 2023 | Support for pytz is now deprecated and will be removed in Django 5.0. |
[52] | 4.13 Aug 2022 | April 2023 | December 2023 | Asynchronous ORM interface, CSRF_COOKIE_MASKED setting, outputting a form, like {{ form }} |
[53] | 4.2 LTS3 Apr 2023 | December 2023 | April 2026 | Psycopg 3 support, ENGINE as django.db.backends.postgresql supports both libraries. |
[54] | 5.04 Dec 2023 | August 2024 | April 2025 | Facet filters in the admin, Simplified templates for form field rendering |
[55] | 5.17 Aug 2024 | April 2025 | December 2025 | Added support for Python 3.13. Added support for PostgreSQL connection pools. |
[56] | 5.2 LTS2 Apr 2025 | December 2025 | April 2028 | Automatic model import in shell, support for composite primary keys |
[57] | 6.0Dec 2025 | August 2026 | April 2027 | |
Old version, not maintained Old version, still maintained Latest version Latest preview version Future version |
DjangoCon
Summarize
Perspective
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;[58] while another is held in the United States in August or September, in various cities.[59] The 2012 DjangoCon took place in Washington, D.C., from September 3 to 8. 2013 DjangoCon was held in Chicago at the Hyatt Regency Hotel and the post-conference Sprints were hosted at Digital Bootcamp, computer training center.[60] The 2014 DjangoCon US returned to Portland, OR from August 30 to 6 September. The 2015 DjangoCon US was held in Austin, TX from September 6 to 11 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 July 17 to 22.[61] The 2017 DjangoCon US was held in Spokane, WA;[62] in 2018 DjangoCon US was held in San Diego, CA.[63] DjangoCon US 2019 was held again in San Diego, CA from September 22 to 27. DjangoCon 2021 took place virtually and in 2022, DjangoCon US returned to San Diego from October 16 to 21. DjangoCon US 2023 was held from October 16 to 20 at the Durham, NC convention center and DjangoCon US 2024 is scheduled to return to Durham for September 22 to 27.[64][65]
Django mini-conferences are usually held every year as part of the Australian Python Conference 'PyCon AU'.[66] Previously, these mini-conferences have been held in:
- Hobart, Australia, in July 2013,
- Brisbane, Australia, in August 2014 and 2015,
- Melbourne, Australia in August 2016 and 2017, and
- Sydney, Australia, in August 2018 and 2019.
Django has spawned user groups and meetups around the world, a notable group is the Django Girls organization, which began in Poland but now has had events in 91 countries.[67][68][69]
Ports to other languages
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:
CMSs based on Django Framework
Django as a framework is capable of building a complete CMS. Some dedicated CMS projects are based upon Django:
- Django CMS[76]
- Wagtail
- Mezzanine
See also
References
Bibliography
External links
Wikiwand - on
Seamless Wikipedia browsing. On steroids.