Skip this tutorial and mark it as “complete” if you’re using Django 2.
This is only meant for students who are learning Django 1.11, as Django changed how it handles url’s in versions 2.0 and above.
We’re about to build our first webpage: a homepage for your blog! But first, let’s learn a little bit about Django URLs.
A URL is simply a web address. You can see a URL every time you visit a website – it is visible in your browser’s address bar. (Yes!
127.0.0.1:8000 is a URL! And
https://commonlounge.com is also a URL.)
Every page on the Internet needs its own URL. This way your application knows what it should show to a user who opens that URL. In Django, we use something called
URLconf(URL configuration). URLconf is a set of patterns that Django will try to match the requested URL to find the correct view.
Let’s open up the
mysite/urls.py file in your code editor of choice and see what it looks like:
"""mysite URL Configuration [...] """ from django.conf.urls import url from django.contrib import admin urlpatterns = [ url(r'^admin/', admin.site.urls), ]
As you can see, Django has already put something here for us.
Lines between triple quotes (
""") are called docstrings – you can write them at the top of a file, class or method to describe what it does. They won’t be run by Python.
The admin URL, which you visited in the previous chapter, is already here:
This line means that for every URL that starts with
admin/, Django will find a corresponding view. In this case, we’re including a lot of admin URLs so it isn’t all packed into this small file – it’s more readable and cleaner.
Do you wonder how Django matches URLs to views? Well, this part is tricky. Django uses
regex, short for “regular expressions”. Regex has a lot (a lot!) of rules that form a search pattern. Since regexes are an advanced topic, we will not go into detail over how they work.
If you still wish to understand how we created the patterns, here is an example of the process – we will only need a limited subset of the rules to express the pattern we are looking for, namely:
^for the beginning of the text
$for the end of the text
\dfor a digit
+to indicate that the previous item should be repeated at least once
()to capture part of the pattern
Anything else in the URL definition will be taken literally.
Now imagine you have a website with the address like
12345 is the number of your post.
Writing separate views for all the post numbers would be really annoying. With regular expressions, we can create a pattern that will match the URL and extract the number for us:
^post/(\d+)/$. Let’s break this down piece by piece to see what we are doing here:
- ^post/ is telling Django to take anything that has
post/at the beginning of the URL (right after
- (\d+) means that there will be a number (one or more digits) and that we want the number captured and extracted
- / tells Django that another
/character should follow
- $ then indicates the end of the URL meaning that only strings ending with the
/will match this pattern
Time to create our first URL! We want ’http://127.0.0.1:8000/’ to be the home page of our blog and to display a list of posts.
We also want to keep the
mysite/urls.py file clean, so we will import URLs from our
blogapplication to the main
Go ahead, add a line that will import
blog.urls. Note that we are using the
include function here so you will need to add that import.
mysite/urls.py file should now look like this:
from django.conf.urls import include from django.conf.urls import url from django.contrib import admin urlpatterns = [ url(r'^admin/', admin.site.urls), url(r'', include('blog.urls')), ]
Django will now redirect everything that comes into http://127.0.0.1:8000/ to
blog.urls and looks for further instructions there.
Writing regular expressions in Python is always done with
r in front of the string. This is a helpful hint for Python that the string may contain special characters that are not meant for Python itself, but for the regular expression instead.
Create a new empty file named
urls.py in the
blog directory. All right! Add these first two lines:
from django.conf.urls import url from . import views
Here we’re importing Django’s function
url and all of our
views from the
blog application. (We don’t have any yet, but we will get to that in a minute!)
After that, we can add our first URL pattern:
urlpatterns = [ url(r'^$', views.post_list, name='post_list'), ]
As you can see, we’re now assigning a
post_list to the
^$ URL. This regular expression will match
^ (a beginning) followed by
$ (an end) – so only an empty string will match. That’s correct, because in Django URL resolvers, ’http://127.0.0.1:8000/’ is not a part of the URL. This pattern will tell Django that
views.post_list is the right place to go if someone enters your website at the ’http://127.0.0.1:8000/’ address.
The last part,
name='post_list', is the name of the URL that will be used to identify the view. This can be the same as the name of the view but it can also be something completely different. We will be using the named URLs later in the project, so it is important to name each URL in the app. We should also try to keep the names of URLs unique and easy to remember.
If you try to visit http://127.0.0.1:8000/ now, then you’ll find some sort of ‘web page not available’ message. This is because the server (remember typing
runserver?) is no longer running. Take a look at your server console window to find out why.
Your console is showing an error, but don’t worry – it’s actually pretty useful: It’s telling you that there is no attribute ‘post_list’. That’s the name of the view that Django is trying to find and use, but we haven’t created it yet. At this stage, your
/admin/will also not work. No worries – we will get there.
If you want to know more about Django URLconfs, look at the official documentation:https://docs.djangoproject.com/en/1.11/topics/http/urls/
Onwards to the next section on Django views!