Django (web framework)
Python web framework From Wikipedia, the free encyclopedia
Python web framework From Wikipedia, the free encyclopedia
Django (/ˈdʒæŋɡoʊ/ JANG-goh; sometimes stylized as django)[6] 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.[7][8] 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] | ||
| Size | 8.9 MB[4] | ||
| Type | Web framework[1] | ||
| License | 3-clause BSD[5] | ||
| 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.[9] 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,[10] Mozilla,[11] Disqus,[12] Bitbucket,[13] Nextdoor[14] and Clubhouse.[15]
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 Simon Willison's internship ended.[16] It was released publicly under a BSD license in July 2005. The framework was named after guitarist Django Reinhardt.[17] Adrian Holovaty is a Romani jazz guitar player inspired in part by Reinhardt's music.[18]
In June 2008, it was announced that a newly formed Django Software Foundation (DSF) would maintain Django in the future.[19]
Despite having its own nomenclature, such as naming the callable objects generating the HTTP responses "views",[7] the core Django framework can be seen as an MVC architecture.[8] 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[22] conventions. More than 5000 packages[23] 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,[24] 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).[25][26] 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.[27] Django officially supports five database backends: PostgreSQL, MySQL, MariaDB, SQLite, and Oracle.[28] Microsoft SQL Server can be used with django-mssql while similarly external backends exist for IBM Db2,[29] SQL Anywhere[30] and Firebird.[31] There is a fork named django-nonrel, which supports NoSQL databases, such as MongoDB and Google App Engine's Datastore.[32]
Django may also be run in conjunction with Python 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.[33]
The Django team will occasionally designate certain releases to be "long-term support" (LTS) releases.[34] 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[35] | End of mainstream support | End of extended support | Notes[36] |
|---|---|---|---|---|
| 0.90[37] | 16 Nov 2005 | |||
| 0.91[38] | 11 Jan 2006 | "new-admin" | ||
| 0.95[39] | 29 Jul 2006 | "magic removal" | ||
| 0.96[40] | 23 Mar 2007 | "newforms", testing tools | ||
| 1.0[41] | 3 Sep 2008 | API stability, decoupled admin, unicode | ||
| 1.1[42] | 29 Jul 2009 | Aggregates, transaction based tests | ||
| 1.2[43] | 17 May 2010 | Multiple db connections, CSRF, model validation | ||
| 1.3[44] | 23 Mar 2011 | 23 Mar 2012 | 26 Feb 2013 | Class based views, staticfiles |
| 1.4 LTS[45] | 23 Mar 2012 | 26 Feb 2013 | 1 Oct 2015 | Time zones, in browser testing, app templates. |
| 1.5[46] | 26 Feb 2013 | 6 Nov 2013 | 2 Sep 2014 | Python 3 Support, configurable user model |
| 1.6[47] | 6 Nov 2013 | 2 Sep 2014 | 1 Apr 2015 | Dedicated to Malcolm Tredinnick, db transaction management, connection pooling. |
| 1.7[48] | 2 Sep 2014 | 1 Apr 2015 | 1 Dec 2015 | Migrations, application loading and configuration. |
| 1.8 LTS[49] | 1 Apr 2015 | 1 Dec 2015 | 1 Apr 2018 | Native support for multiple template engines. Support ended on 1 April 2018 |
| 1.9[50] | 1 Dec 2015 | 1 Aug 2016 | 4 Apr 2017 | Automatic password validation. New styling for admin interface. |
| 1.10[51] | 1 Aug 2016 | 4 Apr 2017 | 2 Dec 2017 | Full text search for PostgreSQL. New-style middleware. |
| 1.11 LTS[52] | 4 Apr 2017 | 2 Dec 2017 | 1 Apr 2020 | Last version to support Python 2.7. Support ended on 1 April 2020 |
| 2.0[53] | 2 Dec 2017 | 1 Aug 2018 | 1 Apr 2019 | First Python 3-only release, Simplified URL routing syntax, Mobile friendly admin. |
| 2.1[54] | 1 Aug 2018 | 1 Apr 2019 | 2 Dec 2019 | Model "view" permission. |
| 2.2 LTS[55] | 1 Apr 2019 | 2 Dec 2019 | 11 Apr 2022 | Security release. |
| 3.0[56] | 2 Dec 2019 | 3 Aug 2020 | 6 Apr 2020 | ASGI support |
| 3.1[57] | 4 Aug 2020 | 6 Apr 2020 | 7 Dec 2021 | Asynchronous views and middleware |
| 3.2 LTS[58] | 6 Apr 2021 | 7 Dec 2021 | April 2024 | Tracking many to many relationships, added support for Python 3.11 |
| 4.0[59] | 7 Dec 2021 | 3 Aug 2022 | April 2023 | Support for pytz is now deprecated and will be removed in Django 5.0. |
| 4.1[60] | 3 Aug 2022 | April 2023 | December 2023 | Asynchronous ORM interface, CSRF_COOKIE_MASKED setting, outputting a form, like {{ form }} |
| 4.2 LTS[61] | 3 Apr 2023 | December 2023 | April 2026 | Psycopg 3 support, ENGINE as django.db.backends.postgresql supports both libraries. |
| 5.0 | 4 Dec 2023 | August 2024 | April 2025 | |
| 5.1[62] | 7 Aug 2024 | April 2025 | December 2025 | |
Old version Older version, still maintained Latest version Latest preview version Future release | ||||
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;[63] while another is held in the United States in August or September, in various cities.[64] 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.[65] 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.[66] The 2017 DjangoCon US was held in Spokane, WA;[67] in 2018 DjangoCon US was held in San Diego, CA.[68] 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.[69][70]
Django mini-conferences are usually held every year as part of the Australian Python Conference 'PyCon AU'.[71] Previously, these mini-conferences have been held in:
Django has spawned user groups and meetups around the world, the most notable group is the Django Girls organization, which began in Poland but now has had events in 91 countries.[72][73][74]
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 a framework is capable of building a complete CMS, however there are dedicated CMS projects which are built upon and extend the Django framework. Below is a list of a few of the more popular Django-based CMSs:
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.
