Jump to content

Django (web framework): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Line 42: Line 42:


===Components===
===Components===
[[File:Django useradmin.png|thumb|Screenshot of the Django admin user interface for modifying a user.]]
[[File:Django useradmin.png|thumb|Screenshot of the Django admin user interface for modifying a user account.]]
Despite having its own nomenclature, such as naming the callable objects generating the response "views",<ref name=faq-mvc /> the core Django framework can be seen as MVC.<ref name=djangobook-mvc /> It consists of an [[object-relational mapping|object-relational mapper]] which mediates between [[data modeling|data models]] (defined as Python classes) and a [[relational database]] ("'''M'''odel"); a system for processing requests with a [[web template system|web templating system]] ("'''V'''iew") and a [[regular expression|regular-expression]]-based [[Uniform Resource Locator|URL]] dispatcher ("'''C'''ontroller").
Despite having its own nomenclature, such as naming the callable objects generating the response "views",<ref name=faq-mvc /> the core Django framework can be seen as MVC.<ref name=djangobook-mvc /> It consists of an [[object-relational mapping|object-relational mapper]] which mediates between [[data modeling|data models]] (defined as Python classes) and a [[relational database]] ("'''M'''odel"); a system for processing requests with a [[web template system|web templating system]] ("'''V'''iew") and a [[regular expression|regular-expression]]-based [[Uniform Resource Locator|URL]] dispatcher ("'''C'''ontroller").


Revision as of 08:03, 12 May 2015

Django
Original author(s)Lawrence Journal-World
Developer(s)Django Software Foundation
Initial release21 July 2005; 19 years ago (2005-07-21)[1]
Stable release2.2.3[2] (1 July 2019; 5 years ago (2019-07-01)) [±]
Preview release2.2 rc1[3] (18 March 2019; 5 years ago (2019-03-18)) [±]
Repository
Written inPython
Size6.92 MB
TypeWeb application framework
License3-clause BSD
Websitedjangoproject.com

Django (/ˈdʒæŋɡoʊ/ JANG-goh)[4] is a free and open source web application framework, written in Python, which follows the model–view–controller (MVC) architectural pattern.[5][6] 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.

Some well-known sites that use Django include Pinterest,[7] Instagram,[8] Mozilla,[9] The Washington Times,[10] Disqus,[11] the Public Broadcasting Service,[12] and Bitbucket.[13]

History

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.[14] It was released publicly under a BSD license in July 2005. The framework was named after guitarist Django Reinhardt.[14]

In June 2008, it was announced that a newly formed Django Software Foundation (DSF) would maintain Django in the future.[15]

Features

Components

Screenshot of the Django admin user interface for modifying a user account.

Despite having its own nomenclature, such as naming the callable objects generating the response "views",[5] the core Django framework can be seen as MVC.[6] 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.

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[18] conventions. More than 2500 packages[19] 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,[20] 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 in conjunction with Apache, NGINX using WSGI, Gunicorn, or Cherokee using flup (a Python module).[21][22] 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.[23] 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.

Google App Engine includes support for Django version 1.x.x[24] as one of the bundled frameworks.

Using Django

Online resources

Books

  • Roy Greenfeld, Daniel; Roy Greenfeld, Audrey (2015), Two Scoops of Django: Best Practices for Django 1.8 (3rd ed.), Two Scoops Press, p. 501
  • 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
  • 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

Main article: List of 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.[25]

Versions

Meaning
Red Not supported
Yellow Still supported
Green Current version
Version history
Version Date Notes
0.90[27] 16 Nov 2005
0.91[28] 11 Jan 2006 "new-admin"
0.95[29] 29 Jul 2006 "magic removal"
0.96[30] 23 Mar 2007 "newforms", testing tools
1.0[31] 3 Sep 2008 API stability, decoupled admin, unicode
1.1[32] 29 Jul 2009 Aggregates, transaction based tests
1.2[33] 17 May 2010 Multiple db connections, CSRF, model validation
1.3[34] 23 Mar 2011 Class based views, staticfiles
1.4[35] 23 Mar 2012 Timezones, in browser testing, app templates. Long-term support release, supported until 1 October 2015[36]
1.5[37] 26 Feb 2013 Python 3 Support, configurable user model
1.6[38] 6 Nov 2013 Dedicated to Malcolm Tredinnick, db transaction management, connection pooling.
1.7[39] 2 Sep 2014 Migrations, application loading and configuration. Will receive security updates until at least October 2015
1.8[40] 1 Apr 2015 Native support for multiple template engines. Long-term support release, supported until at least April 2018

Community

DjangoCon

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;[41] while another is held in the United States in September, usually in Portland, Oregon.[42] 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.[43]

Django mini-conferences were held in Hobart, Australia in July 2013 and Brisbane, Australia in August 2014.[44]

Other languages

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.

See also

Wikimedia Commons has media related to Django (web framework).

References

  1. ^ "Django FAQ". Retrieved 2 September 2014.
  2. ^ Graham, Tim (1 July 2019). "News and Events". Django Weblog. Retrieved 17 July 2019.
  3. ^ Gibson, Carlton (18 March 2019). "Django 2.2 release candidate 1 released". Django Weblog. Retrieved 27 March 2019.
  4. ^ What does "Django" mean, and how do you pronounce it?
  5. ^ a b Django FAQ about MVC in Django
  6. ^ a b 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
  7. ^ Pinterest: What technologies were used to make Pinterest? - Quora
  8. ^ "What Powers Instagram: Hundreds of Instances, Dozens of Technologies".
  9. ^ Python | MDN
  10. ^ Opensource.washingtontimes.com. Retrieved on 2014-05-30.
  11. ^ "Scaling Django to 8 Billion Page Views".
  12. ^ "20 Creative Websites Running Django".
  13. ^ https://code.djangoproject.com/wiki/DjangoSuccessStoryBitbucket
  14. ^ a b "Django's History". The Django Book. Retrieved 6 June 2013.
  15. ^ Announcing the Django Software Foundation
  16. ^ "Security in Django". Django Project. Retrieved 25 March 2013.
  17. ^ Socol, James (2012). "Best Basic Security Practices (Especially with Django)". Retrieved 25 March 2013.
  18. ^ What is a reusable app?
  19. ^ djangopackages.com, an open source package repository for the Django framework
  20. ^ Django design philosophies
  21. ^ Django documentation of deployment
  22. ^ Cookbook: Setting up Django
  23. ^ How to use Django with Apache and mod_wsgi. Official Django documentation.
  24. ^ Running Pure Django Projects on Google App Engine. Code.google.com (2010-11-01). Retrieved on 5 December 2011.
  25. ^ Django development IDEs discussion at Stackoverflow
  26. ^ NetBeans Django Plugin
  27. ^ "Introducing Django 0.90". Django weblog. Retrieved 2 February 2013.
  28. ^ "Django 0.91 released". Django weblog. Retrieved 2 February 2013.
  29. ^ "Introducing Django 0.95". Django weblog. Retrieved 2 February 2013.
  30. ^ "Announcing Django 0.96!". Django weblog. Retrieved 2 February 2013.
  31. ^ "Django 1.0 released!". Django weblog. Retrieved 2 February 2013.
  32. ^ "Django 1.1 released". Django weblog. Retrieved 2 February 2013.
  33. ^ "Django 1.2 released". Django weblog. Retrieved 2 February 2013.
  34. ^ "Django 1.3 released". Django weblog. Retrieved 2 February 2013.
  35. ^ "Django 1.4 released". Django weblog. Retrieved 2 February 2013.
  36. ^ https://docs.djangoproject.com/en/1.7/internals/release-process/#long-term-support-lts-releases
  37. ^ "Django 1.5 released" Django weblog. Retrieved 27 February 2013.
  38. ^ "Django 1.6 released" Django weblog. Retrieved 6 November 2013.
  39. ^ "Django 1.7 released" Django weblog. Retrieved 4 September 2014.
  40. ^ "Django 1.8 released" Django weblog. Retrieved 2 April 2015.
  41. ^ DjangoCon EU series, Lanyrd.com
  42. ^ DjangoCon US series, Lanyrd.com
  43. ^ "DjangoCon". DjangoCon. Retrieved 29 July 2012. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  44. ^ DjangoCon AU 2013. Djangocon.com.au. Retrieved on 2014-05-30.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Django_(web_framework)&oldid=661965477"