Django (web framework)

Python web framework From Wikipedia, the free encyclopedia

Django (web framework)

Django (/ˈæŋɡ/ 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.

Quick Facts Original author(s), Developer(s) ...
Original author(s)Adrian Holovaty, Simon Willison
Developer(s)Django Software Foundation[1]
Initial release21 July 2005; 19 years ago (2005-07-21)[2]
Stable release
5:5.2[3]  / 2 April 2025; 23 days ago (2 April 2025)
Repository
Written inPython[1]
TypeWeb framework[1]
License3-clause BSD[4]
Websitewww.djangoproject.com 
Close

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

Thumb
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",[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:

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.


More information Version, Release date ...
Version Release date[27] End of mainstream support End of extended support Notes[28]
Old version, not maintained: 0.90[29]16 Nov 2005
Old version, not maintained: 0.91[30]11 Jan 2006"new-admin"
Old version, not maintained: 0.95[31]29 Jul 2006"magic removal"
Old version, not maintained: 0.96[32]23 Mar 2007"newforms", testing tools
Old version, not maintained: 1.0[33]3 Sep 2008API stability, decoupled admin, unicode
Old version, not maintained: 1.1[34]29 Jul 2009Aggregates, transaction based tests
Old version, not maintained: 1.2[35]17 May 2010Multiple db connections, CSRF, model validation
Old version, not maintained: 1.3[36]23 Mar 201123 Mar 201226 Feb 2013Class based views, staticfiles
Old version, not maintained: 1.4 LTS[37]23 Mar 201226 Feb 20131 Oct 2015Time zones, in browser testing, app templates.
Old version, not maintained: 1.5[38]26 Feb 20136 Nov 20132 Sep 2014Python 3 Support, configurable user model
Old version, not maintained: 1.6[39]6 Nov 20132 Sep 20141 Apr 2015Dedicated to Malcolm Tredinnick, db transaction management, connection pooling.
Old version, not maintained: 1.7[40]2 Sep 20141 Apr 20151 Dec 2015Migrations, application loading and configuration.
Old version, not maintained: 1.8 LTS[41]1 Apr 20151 Dec 20151 Apr 2018Native support for multiple template engines. Support ended on 1 April 2018
Old version, not maintained: 1.9[42]1 Dec 20151 Aug 20164 Apr 2017Automatic password validation. New styling for admin interface.
Old version, not maintained: 1.10[43]1 Aug 20164 Apr 20172 Dec 2017Full text search for PostgreSQL. New-style middleware.
Old version, not maintained: 1.11 LTS[44]4 Apr 20172 Dec 20171 Apr 2020Last version to support Python 2.7. Support ended on 1 April 2020
Old version, not maintained: 2.0[45]2 Dec 20171 Aug 20181 Apr 2019First Python 3-only release, Simplified URL routing syntax, Mobile friendly admin.
Old version, not maintained: 2.1[46]1 Aug 20181 Apr 20192 Dec 2019Model "view" permission.
Old version, not maintained: 2.2 LTS[47]1 Apr 20192 Dec 201911 Apr 2022Security release.
Old version, not maintained: 3.0[48]2 Dec 20193 Aug 20206 Apr 2020ASGI support
Old version, not maintained: 3.1[49]4 Aug 20206 Apr 20207 Dec 2021Asynchronous views and middleware
Old version, not maintained: 3.2 LTS[50]6 Apr 20217 Dec 2021April 2024Tracking many to many relationships, added support for Python 3.11
Old version, not maintained: 4.0[51]7 Dec 20213 Aug 2022April 2023Support for pytz is now deprecated and will be removed in Django 5.0.
Old version, not maintained: 4.1[52]3 Aug 2022April 2023December 2023Asynchronous ORM interface, CSRF_COOKIE_MASKED setting, outputting a form, like {{ form }}
Old version, still maintained: 4.2 LTS[53]3 Apr 2023December 2023April 2026Psycopg 3 support, ENGINE as django.db.backends.postgresql supports both libraries.
Old version, still maintained: 5.0[54]4 Dec 2023August 2024April 2025Facet filters in the admin, Simplified templates for form field rendering
Old version, still maintained: 5.1[55]7 Aug 2024April 2025December 2025Added support for Python 3.13. Added support for PostgreSQL connection pools.
Latest version: 5.2 LTS[56]2 Apr 2025December 2025April 2028Automatic model import in shell, support for composite primary keys
Future version: 6.0[57]Dec 2025August 2026April 2027
Legend:
Old version, not maintained
Old version, still maintained
Latest version
Latest preview version
Future version
Close

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:

See also

References

Bibliography

Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.