URL namespacing in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What URL does this namespaced Django URL pattern resolve to?

Given the following Django URL configuration, what is the full URL path for the named URL blog:post_detail with post_id=5?

Django

from django.urls import path, include

# blog/urls.py
app_name = 'blog'
urlpatterns = [
    path('post/<int:post_id>/', lambda request: None, name='post_detail'),
]

# project/urls.py
urlpatterns = [
    path('blog/', include('blog.urls')),
]

A /blog/post_detail/5/

B /blog/post/5/

C /post_detail/5/

D /post/5/

💡 Hint

Remember that the app_name defines the namespace and the include path prefix is added before the app URLs.

The app_name 'blog' sets the namespace. The include('blog.urls') is under the path 'blog/'. So the named URL blog:post_detail with post_id=5 resolves to '/blog/post/5/'.

📝 Syntax

intermediate

Which option correctly defines a namespaced URL pattern in Django?

Which of the following code snippets correctly sets up URL namespacing in a Django app?

A

app_name = 'shop'
urlpatterns = [
    path('item/<int:id>/', view, name='item_detail'),
]

B

urlpatterns = [
    path('item/<int:id>/', view, name='shop:item_detail'),
]

C

app_name = 'shop'
urlpatterns = [
    path('item/<int:id>/', view, name='shop:item_detail'),
]

D

app_name = 'shop'
urlpatterns = [
    path('item/<int:id>/', view, name='item_detail'),
]
include('shop.urls', namespace='shop')

💡 Hint

Remember that app_name sets the namespace and name in path should be simple, without namespace prefix.

Option A correctly sets app_name and uses a simple name in the path. Option A incorrectly prefixes the name with namespace. Option A repeats the namespace in name. Option A misuses include inside urlpatterns.

🔧 Debug

advanced

Why does reversing 'store:product_detail' raise NoReverseMatch error?

Given this setup, why does reverse('store:product_detail', kwargs={'pk': 10}) raise a NoReverseMatch error?

Django

# store/urls.py
app_name = 'store'
urlpatterns = [
    path('product/<int:id>/', view, name='product_detail'),
]

# project/urls.py
urlpatterns = [
    path('shop/', include('store.urls')),
]

A The namespace 'store' is not correctly set in the included URLs.

B The reverse call uses args but the URL pattern requires kwargs with 'id'.

C The URL pattern uses 'id' but reverse expects 'pk' as argument name.

D The include path prefix 'shop/' does not match the namespace 'store'.

💡 Hint

Check how the URL pattern parameters and reverse arguments match.

The URL pattern defines <int:id>, so when using keyword arguments in reverse, the key must be 'id'. Using kwargs={'pk': 10} fails to match the parameter name, raising NoReverseMatch. Option C identifies this mismatch. Positional args=[10] would also work.

❓ state_output

advanced

What is the output of this Django template URL tag with namespaces?

Given the URL configuration below, what will this Django template output?

{% url 'accounts:login' %}

Django

# accounts/urls.py
app_name = 'accounts'
urlpatterns = [
    path('login/', view, name='login'),
]

# project/urls.py
urlpatterns = [
    path('user/', include('accounts.urls')),
]

A /user/login/

B /accounts/login/

C /user/accounts/login/

D /login/

💡 Hint

Remember the include path prefix is added before the app URLs.

The namespace 'accounts' corresponds to the included URLs under 'user/'. The named URL 'login' is 'login/'. So the full URL is '/user/login/'.

🧠 Conceptual

expert

Why use URL namespacing in Django projects?

Which of the following is the best explanation for why Django uses URL namespacing?

A To automatically generate URLs without defining them explicitly in each app's urls.py.

B To speed up URL resolution by caching namespace lookups.

C To enforce security by restricting URL access based on namespaces.

D To allow multiple apps to use the same URL names without conflicts by grouping them under unique namespaces.

💡 Hint

Think about how large projects with many apps avoid URL name clashes.

URL namespacing allows different apps to define the same URL names without clashing by grouping them under unique namespaces. This helps in reversing URLs unambiguously.