Django (web framework)
||This article is in a list format that may be better presented using prose. (December 2014)|
|Original author(s)||Lawrence Journal-World|
|Developer(s)||Django Software Foundation|
|Initial release||21 July 2005|
|Stable release||1.7.4 (January 27, 2015 ) [±]|
|Preview release||1.8 alpha 1 (January 16, 2015 ) [±]|
|Type||Web application framework|
Django (// JANG-goh) is a free and open source web application framework, written in Python, which follows the model–view–controller (MVC) architectural pattern. It is maintained by the Django Software Foundation (DSF), an independent organization established as a 501(c)(3) non-profit.
Django's primary goal is to ease the creation of complex, database-driven websites. Django emphasizes reusability and "pluggability" of components, 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 born 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. It was released publicly under a BSD license in July 2005. The framework was named after guitarist Django Reinhardt.
Despite having its own nomenclature, such as naming the callable objects generating the response "views", the core Django framework can be seen as MVC. It consists of an object-relational mapper which mediates between data models (defined as Python classes) and a relational database ("Model"); a system for processing 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 which 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 which can use any of several cache methods.
- Support for middleware classes which can intervene at various stages of request processing and carry out custom functions.
- An internal dispatcher system which 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 which 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.
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 Google 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.
- A framework for creating GIS applications.
|This section relies too much on references to primary sources. (January 2015)|
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: 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 four database backends: PostgreSQL, MySQL, SQLite, and Oracle. Microsoft SQL Server can be used with django-mssql but only in 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 provides functionality to compile Django in to a .war suitable for deployment.
||This article contains instructions, advice, or how-to content. (February 2015)|
- Django Official Documentation - Current and detailed documentation on nearly every aspect of Django. It includes a version selector for information pertaining to specific versions of Django.
- Tango with Django - A beginner's guide to web development with Django.
- Two Scoops - Making Python and Django as fun as ice cream.
- Django Packages - A directory of reusable apps, sites, tools, and more for Django projects.
- Django Basics - Installing Django and Setting Up a Project and an App
- Percival, Harry (2014), Test-Driven Development with Python (1st ed.), O'Reilly Media, p. 480, ISBN 1449364829
- Greenfeld, Daniel; Roy, Audrey (February 2014), Two Scoops of Django: Best Practices for Django 1.6 (2nd ed.), Two Scoops Press, p. 446, ISBN 098146730X
- Alchin, Marty (10 July 2013), Pro Django (2nd ed.), Apress, p. 300, ISBN 1-430-25809-8
- McGaw, Jim (29 October 2009), Beginning Django E-Commerce (1st ed.), Apress, p. 300, ISBN 1-430-22535-1
- Bennett, James (24 June 2009), Practical Django Projects (2nd ed.), Apress, p. 272, ISBN 1-430-21938-6
- Forcier, Jeff; Bissex, Paul; Chun, Wesley (3 November 2008), Python Web Development with Django (1st ed.), Addison-Wesley, p. 408, ISBN 0-13-235613-9, OCLC 213835556
Integrated development environments for Python
While a number of Django developers use text editors such as Vim, Emacs, TextMate or Sublime with Django Bundle for their projects, others prefer python-specific tools providing debugging, refactoring, unit testing, etc.
- Aptana Studio with integrated PyDev
- Eclipse with PyDev
- Eric Python IDE
- IntelliJ IDEA with Django plugin, provides functionality similar to PyCharm
- Komodo IDE
- Microsoft Visual Studio with Python Tools for Visual Studio
- NetBeans with Django Plugin
- Ninja IDE
- Spyder (software)
- Wing IDE
|0.90||16 Nov 2005|
|0.91||11 Jan 2006||"new-admin"|
|0.95||29 Jul 2006||"magic removal"|
|0.96||23 Mar 2007||"newforms", testing tools|
|1.0||3 Sep 2008||API stability, decoupled admin, unicode|
|1.1||29 Jul 2009||Aggregates, transaction based tests|
|1.2||17 May 2010||Multiple db connections, CSRF, model validation|
|1.3||23 Mar 2011||Class based views, staticfiles|
|1.4||23 Mar 2012||Timezones, in browser testing, app templates. Long-term support release, supported until at least March 2015|
|1.5||26 Feb 2013||Python 3 Support, configurable user model|
|1.6||6 Nov 2013||Dedicated to Malcolm Tredinnick, db transaction management, connection pooling|
|1.7||2 Sep 2014||Migrations, application loading and configuration|
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 September, usually in Portland, Oregon. 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.
Django mini-conferences were held in Hobart, Australia in July 2013 and Brisbane, Australia in August 2014.
Django's template design has been ported to other languages besides Python, providing decent cross-platform support. Some of these options are more direct ports, while others are inspired by Django, retaining its concepts but taking greater liberties to deviate from Django's design.
|Wikimedia Commons has media related to Django (web framework).|
- "Django FAQ". Retrieved 2 September 2014.
- Graham, Tim (27 January 2015). "Bugfix releases issued: 1.7.4 and 1.4.19". Django Weblog. Retrieved 27 January 2015.
- Graham, Tim (16 January 2015). "Django 1.8 alpha 1 released". Django Weblog. Retrieved 17 January 2015.
- What does "Django" mean, and how do you pronounce it?
- Django FAQ about MVC in Django
- Adrian Holovaty, Jacob Kaplan-Moss, et al. The Django Book.
Django follows this MVC pattern closely enough that it can be called an MVC framework
- Pinterest: What technologies were used to make Pinterest? - Quora
- "What Powers Instagram: Hundreds of Instances, Dozens of Technologies".
- Python | MDN
- Opensource.washingtontimes.com. Retrieved on 2014-05-30.
- "Scaling Django to 8 Billion Page Views".
- "20 Creative Websites Running Django".
- "Django's History". The Django Book. Retrieved 6 June 2013.
- Announcing the Django Software Foundation
- "Security in Django". Django Project. Retrieved March 25, 2013.
- Socol, James (2012). "Best Basic Security Practices (Especially with Django)". Retrieved March 25, 2013.
- What is a reusable app?
- djangopackages.com, an open source package repository for the Django framework
- Django design philosophies
- Django documentation of deployment
- Cookbook: Setting up Django
- How to use Django with Apache and mod_wsgi. Official Django documentation.
- Running Pure Django Projects on Google App Engine. Code.google.com (2010-11-01). Retrieved on 5 December 2011.
- Django development IDEs discussion at Stackoverflow
- NetBeans Django Plugin
- "Introducing Django 0.90". Django weblog. Retrieved 2 February 2013.
- "Django 0.91 released". Django weblog. Retrieved 2 February 2013.
- "Introducing Django 0.95". Django weblog. Retrieved 2 February 2013.
- "Announcing Django 0.96!". Django weblog. Retrieved 2 February 2013.
- "Django 1.0 released!". Django weblog. Retrieved 2 February 2013.
- "Django 1.1 released". Django weblog. Retrieved 2 February 2013.
- "Django 1.2 released". Django weblog. Retrieved 2 February 2013.
- "Django 1.3 released". Django weblog. Retrieved 2 February 2013.
- "Django 1.4 released". Django weblog. Retrieved 2 February 2013.
- "Django 1.5 released" Django weblog. Retrieved 27 February 2013.
- "Django 1.6 released" Django weblog. Retrieved 6 November 2013.
- "Django 1.7 released" Django weblog. Retrieved 4 September 2014.
- DjangoCon EU series, Lanyrd.com
- DjangoCon US series, Lanyrd.com
- "DjangoCon". DjangoCon. Retrieved 29 July 2012.
- DjangoCon AU 2013. Djangocon.com.au. Retrieved on 2014-05-30.