This tutorial begins where Tutorial 7 left off.\nWe’ve built our web-poll application and will now look at third-party packages.\nOne of Django’s strengths is the rich ecosystem of third-party packages.\nThey’re community developed packages that can be used to quickly improve the\nfeature set of an application.
\nThis tutorial will show how to add Django Debug Toolbar, a commonly used third-party package. The Django Debug\nToolbar has ranked in the top three most used third-party packages in the\nDjango Developers Survey in recent years.
\n\nDjango Debug Toolbar is a useful tool for debugging Django web applications.\nIt’s a third-party package that is maintained by the community organization\nDjango Commons. The toolbar helps you\nunderstand how your application functions and to identify problems. It does so\nby providing panels that provide debug information about the current request\nand response.
\nTo install a third-party application like the toolbar, you need to install\nthe package by running the below command within an activated virtual\nenvironment. This is similar to our earlier step to install Django.
\nLinux / macOS
$ python -m pip install django-debug-toolbar\nWindows
...\\> py -m pip install django-debug-toolbar\nThird-party packages that integrate with Django need some post-installation\nsetup to integrate them with your project. Often you will need to add the\npackage’s Django app to your INSTALLED_APPS setting. Some packages\nneed other changes, like additions to your URLconf (urls.py).
Django Debug Toolbar requires several setup steps. Follow them in its\ninstallation guide.\nThe steps are not duplicated in this tutorial, because as a third-party\npackage, it may change separately to Django’s schedule.
\nOnce installed, you should be able to see the DjDT «handle» on the right side\nof the browser window when you browse to http://localhost:8000/admin/.\nClick it to open the debug toolbar and use the tools in each panel. See the\npanels documentation page for more information on what the panels show.
At some point you will run into a problem, for example the\ntoolbar may not render. When this happens and you’re unable to\nresolve the issue yourself, there are options available to you.
\nIf the problem is with a specific package, check if there’s a\ntroubleshooting guide or FAQ in the package’s documentation. For example the\nDjango Debug Toolbar has a Tips section that\noutlines troubleshooting options.
Search for similar issues on the package’s issue tracker. Django Debug\nToolbar’s is on GitHub.
Consult the Django Forum.
Join the Django Discord server.
There are many more third-party packages, which you can find using the\nfantastic Django resource, Django Packages.
\nIt can be difficult to know what third-party packages you should use. This\ndepends on your needs and goals. Sometimes it’s fine to use a package that’s\nin its alpha state. Other times, you need to know it’s production ready.\nAdam Johnson has a blog post that outlines\na set of characteristics that qualifies a package as «well maintained».\nDjango Packages shows data for some of these characteristics, such as when the\npackage was last updated.
\nAs Adam points out in his post, when the answer to one of the questions is\n«no», that’s an opportunity to contribute.
\nΟ οδηγός για αρχάριους τελειώνει κάπου εδώ. Στο μεταξύ μπορείτε να δείτε προτεινόμενες κατευθύνσεις για το τι να κάνετε έπειτα, στο άρθρο τι να κάνω μετά από εδώ.
\nΑν είστε εξοικειωμένοι με το Python packaging και ενδιαφέρεστε να μάθετε πως να μετατρέψετε την εφαρμογή ψηφοφορίας σε «επαναχρησιμοποιήσιμη εφαρμογή», δείτε το άρθρο Οδηγός για προχωρημένους: Πως να γράψετε επαναχρησιμοποιήσιμα apps.
\n