Professional Documents
Culture Documents
Django
Written in Python
Size 8.6 MB[3]
Contents
1History
2Features
o 2.1Components
o 2.2Bundled applications
o 2.3Extensibility
o 2.4Server arrangements
3Version history
4Development tools with Django support
5Community
6Ports to other languages
7See also
8References
9Bibliography
10External links
History[edit]
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. [15] It was released publicly under
a BSD license in July 2005. The framework was named after guitarist Django
Reinhardt.[16]
In June 2008, it was announced that a newly formed Django Software
Foundation (DSF) would maintain Django in the future.[17]
Features[edit]
Components[edit]
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:
Django's configuration system allows third party code to be plugged into a regular
project, provided that it follows the reusable app [20] conventions. More than 2500
packages[21] 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, [22] 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[edit]
Django can be run in conjunction with Apache, Nginx using WSGI, Gunicorn,
or Cherokee using flup (a Python module).[23][24] 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.[25] Django officially supports four database
backends: PostgreSQL, MySQL, SQLite, and Oracle. Microsoft SQL Server can be
used with django-mssql on Microsoft operating systems,[26] while similarly external
backends exist for IBM Db2,[27] SQL Anywhere[28] and Firebird.[29] There is a fork named
django-nonrel, which supports NoSQL databases, such as MongoDB and Google
App Engine's Datastore.[30]
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. [31]
Google App Engine includes support for Django version 1.x.x [32] as one of the bundled
frameworks.
Version history[edit]
The Django team will occasionally designate certain releases to be “long-term
support” (LTS) releases.[33] 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.
16 Nov
0.90[36]
2005
23 Mar
0.96[39] "newforms", testing tools
2007
23 Mar
1.3[43] Class based views, staticfiles
2011
23 Mar
1.4 LTS[44] Timezones, in browser testing, app templates.
2012
1.9[49] 1 Dec 2015 Automatic password validation. New styling for admin interface.
1.10[50] 1 Aug 2016 Full text search for PostgreSQL. New-style middleware.
1.11
4 Apr 2017 Last version to support Python 2.7. Support ended on 1 April 2020
LTS[51]
First Python 3-only release, Simplified URL routing syntax, Mobile friendly
2.0[52] 2 Dec 2017
admin.
2.2 LTS[54] 1 Apr 2019 Security release. Supported until at least April 2022
Old version
Latest version
Future release
Community[edit]
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;[57] while another is held in the United States in August or
September, in various cities.[58] 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.[59] 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.[60]The 2017 DjangoCon US was held in Spokane, WA [61]; in 2018 DjangoCon
US was held in San Diego, CA.[62] DjangoCon US 2019 was held again in San Diego,
CA from Sept 22–27.
Django mini-conferences are usually held every year as part of the Australian Python
Conference 'PyCon AU'.[63] Previously, these mini-conferences have been held in:
Liquid for Ruby[67]
Template::Swig for Perl[68]
Twig for PHP and JavaScript[69][70]
Jinja for Python[71]
ErlyDTL for Erlang[72]
See also[edit]
References[edit]
1. ^ "Django FAQ". Retrieved 27 March 2019.
2. ^ https://github.com/django/django/releases
3. ^ "Django Download". Retrieved 5 May 2020.
4. ^ "FAQ: General - Django documentation - Django". Retrieved 30
April 2016.
5. ^ Jump up to:a b "FAQ: General - Django documentation - Django".
Retrieved 30 April2016.
6. ^ Jump up to: Adrian Holovaty, Jacob Kaplan-Moss; et al. The
a b
Bibliography[edit]
Roy Greenfeld, Daniel; Roy Greenfeld, Audrey (2015), Two Scoops of
Django: Best Practices for Django 1.8 (3rd ed.), Two Scoops Press,
p. 531, ISBN 0981467342
Jaiswal, Sanjeev; Kumar, Ratan (22 June 2015), Learning Django
Web Development (1st ed.), Packt, p. 405, ISBN 1783984406
Ravindrun, Arun (31 March 2015), Django Design Patterns and Best
Practices (1st ed.), Packt, p. 180, ISBN 1783986646
Osborn, Tracy (May 2015), Hello Web App (1st ed.), Tracy Osborn,
p. 142, ISBN 0986365912
Bendoraitis, Aidas (October 2014), Web Development with Django
Cookbook (1st ed.), Packt, p. 294, ISBN 178328689X
Baumgartner, Peter; Malet, Yann (2015), High Performance
Django (1st ed.), Lincoln Loop, p. 184, ISBN 1508748128
Elman, Julia; Lavin, Mark (2014), Lightweight Django (1st ed.),
O'Reilly Media, p. 246, ISBN 149194594X
Percival, Harry (2014), Test-Driven Development with Python (1st ed.),
O'Reilly Media, p. 480, ISBN 1449364829
External links[edit]
Wikimedia Commons has
media related to Django
(web framework).
Official website
show
Python web frameworks
show
Web frameworks
Categories:
Free software programmed in Python
Python web frameworks
Software using the BSD license
Navigation menu
Not logged in
Talk
Contributions
Create account
Log in
Article
Talk
Read
Edit
View history
Search
Search Go
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
In other projects
Wikimedia Commons
Print/export
Create a book
Download as PDF
Printable version
Languages
العربية
বাংলা
Español
Français
മലയാളം
Português
Русский
தமிழ்
中文
19 more
Edit links
This page was last edited on 11 May 2020, at 06:42 (UTC).
Text is available under the Creative Commons Attribution-ShareAlike License;
additional terms may apply. By using this site, you agree to the Terms of
Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia
Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Statistics
Cookie statement
Mobile view