Django 面接の質問と回答

質問 36. What are signals in Django?

Signals are pieces of code that hold information regarding what is happening. You can use a dispatcher for sending the signals and listening to those signals. 

The signals become very useful when we want to do something with the data, before or after a certain event occurs.

Here is the list of events on which we can use the Django signals:

• pre_save() trigger before save().
• post_save() trigger after save().
• pre_delete() trigger before delete().
• post_delete() trigger after delete().
• m2m_changed() triggers when there is a change in ManyToMany Field.
• request_started() trigger when the django starts the HTTP request.
• request_finished() trigger when the django finishes the HTTP request.

質問 37. What are some important parameters of signals?

The following are the two important parameters of signals:

• Receiver: It specifies the callback function connected to the signal
• Sender: It specifies a particular sender from where a signal is received

質問 38. What is mixin in Django?

Mixin is a type of multiple inheritances that combines the behaviors and attributes of more than one parent class. It provides an excellent way of reusing the code from multiple classes.

For example, generic class-based views have a mixin called TemplateResponseMixin. This mixin is used for defining the render_to_response() method. When you combine it with a class present in the View, it results in a TemplateView class.

The only drawback of mixin is that it becomes difficult to analyze what a child class is doing and which methods to override if its code scatters between multiple classes.

質問 39. What are caching strategies in Django?

Caching implies storing the output of calculations to avoid performing the same calculations repetitively. Django comes with a robust cache system helping to create dynamic pages. Therefore, it eliminates the need to evaluate pages repeatedly for every request. The following table highlights some of the significant caching strategies:

質問 40. What is the manage.py file in Django?

Whenever you create a project, the manage.py file is automatically created. This is a command-line utility, helping you to interact with your Django project. It performs the same work as Django-admin and sets the DJANGO_SETTINGS_MODULE environment variable to point to your project’s settings. It is better if you use manage.py instead of Django-admin if you are working on a single project.