gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”

gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”

gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”

gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”

gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”

gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”

gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”

gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”

gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”

gets passed a request object – which contains request metadata – and the values captured in the pattern. For example, if a user requested the URL “/articles/2005/05/39323/”, Django would call the function that contains a URL pattern. When processing a request, Django starts at the first pattern in urlpatterns and makes its way down the list, comparing the requested URL against each pattern until it finds one page=3, the URLconf will also look for myapp/. path() argument: view When Django finds a matching pattern, it calls the specified view function with an HttpRequest object as the first argument and any “captured”