Understanding Django Views, request, and render() — Beginner Friendly Guide

[Rajeev Bagra]

 

When learning Django, one of the first things you see is something like this:

# views.py

from django.shortcuts import render

def add(request):
    return render(request, "tasks/add.html")

At first glance, it raises important questions:

• What is request?
• Who sends it?
• What does render() return?
• How does this function become a web page?

Let’s break it down step by step.

---

📂 Initial Project Context

Assume we have a Django app called tasks.

Our structure looks like this:

project/
│
├── tasks/
│   ├── views.py
│   ├── urls.py
│   └── templates/
│       └── tasks/
│           └── add.html
│
└── manage.py

---

🧩 Step 1: The View Function

Inside views.py:

from django.shortcuts import render

def add(request):
    return render(request, "tasks/add.html")

Important:

• add is just a normal Python function.
• It becomes a “view” only when connected to a URL.
• request is automatically provided by Django.

---

🌐 Step 2: Connecting It in urls.py

Inside tasks/urls.py:

from django.urls import path
from . import views

app_name = "tasks"

urlpatterns = [
    path("add/", views.add, name="add"),
]

Now, when a user visits:

http://127.0.0.1:8000/add/

Django:

1. Matches "add/" in urls.py
2. Calls views.add(request)
3. Returns an HTTP response

Without this URL mapping, the function would never run.

---

📌 What Is request?

request is an instance of:

django.http.HttpRequest

Django automatically creates it when a browser sends a request.

It contains:

• request.method → “GET” or “POST”
• request.GET → URL query data
• request.POST → Form data
• request.user → Logged-in user
• request.headers → HTTP headers
• request.session → Session data

Example:

if request.method == "POST":
    task = request.POST["task"]

You never create the request object — Django injects it.

---

🔄 What Does render() Do?

When you write:

return render(request, "tasks/add.html")

Django does three things:

1. Loads the template
2. Converts it to HTML
3. Wraps it inside an HttpResponse

Internally, it’s similar to:

from django.template.loader import get_template
from django.http import HttpResponse

template = get_template("tasks/add.html")
html = template.render({}, request)
return HttpResponse(html)

So render() returns:

HttpResponse

---

🔁 Full Request–Response Flow

When a user visits /add/:

Browser
   ↓
Django server receives request
   ↓
Django creates HttpRequest object
   ↓
URL dispatcher checks urls.py
   ↓
Calls views.add(request)
   ↓
render() creates HttpResponse
   ↓
Django sends HTML back to browser

Django is fundamentally a:

Request → Process → Response

machine.

---

📝 Example add.html

<h1>Add Task</h1>

<form method="post">
    {% csrf_token %}
    <input type="text" name="task">
    <input type="submit" value="Add Task">
</form>

Notice:

• method="post" → sends form data
• {% csrf_token %} → required for security in Django

---

🔥 Why Django Requires request Parameter

If you remove request:

def add():

You’ll get an error:

TypeError: add() takes 0 positional arguments but 1 was given

Because Django always calls:

add(request)

Django controls the function call — not you.

---

🆚 Django vs Flask Routing Difference

In Flask:

@app.route("/add")
def add():
    return render_template("add.html")

The decorator connects the route.

In Django:

• views.py → logic
• urls.py → routing

Django separates concerns more strictly.

---

📚 Official Documentation (Highly Recommended)

Here are the most relevant official Django docs:

1️⃣ Writing Views

https://docs.djangoproject.com/en/stable/topics/http/views/

2️⃣ The HttpRequest Object

https://docs.djangoproject.com/en/stable/ref/request-response/#httprequest-objects

3️⃣ The HttpResponse Object

https://docs.djangoproject.com/en/stable/ref/request-response/#httpresponse-objects

4️⃣ URL Dispatcher

https://docs.djangoproject.com/en/stable/topics/http/urls/

5️⃣ Django Forms (Next Step)

https://docs.djangoproject.com/en/stable/topics/forms/

---

🎯 Key Takeaways

✔ A Django view is just a Python function
✔ It becomes accessible only via urls.py
✔ Django automatically creates and passes the request object
✔ render() returns an HttpResponse
✔ Django works as a Request–Response framework

[Author]

Posts