articles/2025/django-views/

[giscus[bot]]

articles/2025/django-views/

Why I only use Django's base View class instead of generic class-based views or function-based views.

https://www.loopwerk.io/articles/2025/django-views/?utm_campaign=Django%2BNewsletter&utm_medium=email&utm_source=Django_Newsletter_300

[jfmatth]

Nice article, thanks for sharing.

[MHLut]

Interesting idea, and I'm trying this approach now in one of my hobby projects.

One request for the implementation examples: also add the import paths for the Django requirements, like TemplateResponse.

[kevinrenskers]

Good point! I've updated the article.

[danilovmy]

A funny article. The author doesn't want to remember other “magic” methods and still uses magic such as get_object_or_404, redirect, or something else.
And if the author wants to avoid code duplication, he puts the code in “dispatch.” How did he change dispatch? Using the same code as is in get_object method from SingleObjectMixin. Probably, a one-line mixin in the class definition is easier than import + method override + ...

The author's approach shows that he probably does not understand an important idea of GCBV: the declarative way.

A declarative way means less testing.
A declarative way means less complexity (for example, you can use Halstead metrics).
A declarative way means less cyclomatic complexity.
A declarative way means less documentation.

I agree with this article if the author earns money based on the number of lines of code. In this case, Black-formatter can also help to get many more lines.

[kevinrenskers]

I actually explicitly said that I don’t use the dispatch method myself. It’s just there to point out the “textbook” solution.

Also, how are get_object_or_404 and redirect "magic"? They are the complete opposite! You explicitly import them, you call them yourself, there is absolutely no magic involved. Such a bad faith argument you're making here.

It’s fine if you don’t agree with the article, but there is no need for your sarcasm.