{"id":75858,"date":"2020-01-20T12:23:14","date_gmt":"2020-01-20T06:53:14","guid":{"rendered":"https:\/\/www.vskills.in\/certification\/tutorial\/?p=75858"},"modified":"2024-04-12T14:17:40","modified_gmt":"2024-04-12T08:47:40","slug":"the-django-standard-library-2","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/the-django-standard-library-2\/","title":{"rendered":"The Django Standard Library"},"content":{"rendered":"

Django\u2019s standard library lives in the package django.contrib. Within each subpackage is a separate piece of add-on functionality. These pieces are not necessarily related, but some django.contrib subpackages may require other ones.<\/p>\n

There\u2019s no hard requirement for the types of functionality in django.contrib. Some of the packages include models (and hence require you to install their database tables into your database), but others consist solely of middleware or template tags. The single characteristic the django.contrib packages have in common is this: if you were to remove the django.contrib package entirely, you could still use Django\u2019s fundamental features with no problems. When the Django developers add new functionality to the framework, they use this rule of thumb in deciding whether the new functionality should live in django.contrib or elsewhere. django.contrib consists of these packages:<\/p>\n