I would like to know if there is any difference in practice between these two architectures.
I would like to know if there is any difference in practice between these two architectures.
Basically 'and nomenclature issue, the django view' is exactly the equivalent of the controler in MVC. The template (M T V) and the html file rendered by the view (controller) would be the equivalent of the view in MVC
Model (models.py) Template (rendered HTML file) View (controller-equivalent views.py in MVC)
This is just a more conceptual question. The Django developers understand that the controller is the framework itself. If we stop to think this makes sense, since when you access some url of your application, the Django engine itself redirects to the correct view, as you defined it in the url settings, ie it is understood here that the role controller is already running automatically. So the method or class that will render what will happen when this particular page is accessed was called view. Finally, the way your page will be displayed (using the view variable dictionary) is a template.
I really hope I have helped!