@@ -48,13 +48,20 @@ <h1>Django</h1>
4848< p > < a href ="http://www.djangoproject.com/ "> Django</ a > is a widely used Python web
4949application framework with a "batteries-included" philosophy. The principle
5050behind batteries-included is that the common functionality for building
51- web applications should come with the framework instead of as a separate
52- library. For example,
51+ web applications should come with the framework instead of as separate
52+ libraries. </ p >
53+ < p > For example,
54+ < a href ="https://docs.djangoproject.com/en/dev/topics/auth/ "> authentication</ a > ,
5355< a href ="https://docs.djangoproject.com/en/dev/topics/http/urls/ "> URL routing</ a > , a
5456< a href ="https://docs.djangoproject.com/en/dev/topics/templates/ "> templating system</ a > ,
5557< a href ="https://docs.djangoproject.com/en/dev/topics/db/ "> object-relational mapper</ a > ,
5658and < a href ="https://docs.djangoproject.com/en/dev/topics/migrations/ "> database schema migrations</ a >
57- (as of version 1.7) are all included with the < a href ="https://pypi.python.org/pypi/Django/1.6.2 "> Django framework</ a > .</ p >
59+ (as of version 1.7) are all included with the < a href ="https://pypi.python.org/pypi/Django/1.6.2 "> Django framework</ a > .
60+ Compare that functionality to the Flask framework which requires a separate
61+ library such as < a href ="https://flask-login.readthedocs.org/en/latest/ "> Flask-Login</ a >
62+ to perform user authentication. The batteries-includes and extensibility
63+ philosophies are simply two different ways to tackle framework building.
64+ Neither philosophy is inherently better than the other.</ p >
5865< h2 > Why is Django a good web framework choice?</ h2 >
5966< p > The Django project's stability, performance and community have grown
6067tremendously over the past decade since the framework's creation. Detailed
0 commit comments