node = NavigationNode( title=poll.question, url=reverse("polls:detail", args=(poll.pk,)), id=poll.pk, # unique id for this node within the menu menu ) nodes.append(node) return nodes What’s happening here: we define a PollsMenu class, and register it we give the class a name attribute (will be displayed in admin) only be required on the subset of nodes left after cutting. Nodes Nodes are assembled in a tree. Each node is an instance of the menus.base.NavigationNode class. A NavigationNode has attributes such as URL

node = NavigationNode( title=poll.question, url=reverse("polls:detail", args=(poll.pk,)), id=poll.pk, # unique id for this node within the menu menu ) nodes.append(node) return nodes What’s happening here: we define a PollsMenu class, and register it we give the class a name attribute (will be displayed in admin) only be required on the subset of nodes left after cutting. Nodes Nodes are assembled in a tree. Each node is an instance of the menus.base.NavigationNode class. A NavigationNode has attributes such as URL

to refer to the apphook. You can see from Django Polls [https://github.com/divio/django-polls/blob/master/polls/urls.py#L6] that the application namespace polls is hard-coded into the application, so this node = NavigationNode( title=poll.question, url=reverse('polls:detail', args=(poll.pk,)), id=poll.pk, # unique id for this node within the menu menu ) nodes.append(node) return nodes menu_pool.register_menu(PollsMenu) What’s happening here: we define a PollsMenu class, and register it we give the class a name

to refer to the apphook. You can see from Django Polls [https://github.com/divio/django-polls/blob/master/polls/urls.py#L6] that the application namespace polls is hard-coded into the application, so this node = NavigationNode( title=poll.question, url=reverse('polls:detail', args=(poll.pk,)), id=poll.pk, # unique id for this node within the menu menu ) nodes.append(node) return nodes menu_pool.register_menu(PollsMenu) What’s happening here: we define a PollsMenu class, and register it we give the class a name

2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Stable branches Tags How is Django Formed? Overview Prerequisites Pre-release tasks Preparing all the documentation for that release. If you’re using the development version of Django (aka the master branch), the docs/ directory contains all of the documentation. You can update your Git checkout will be placed in docs/_build/html. Differences between versions The text documentation in the master branch of the Git repository contains the “latest and greatest” changes and additions. These changes

2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Other branches Tags How is Django Formed? Overview Prerequisites Pre-release tasks Preparing all the documentation for that release. If you’re using the development version of Django (aka the master branch), the docs/ directory contains all of the documentation. You can update your Git checkout will be placed in docs/_build/html. Differences between versions The text documentation in the master branch of the Git repository contains the “latest and greatest” changes and additions. These changes

Documentation, Release 2.1.16.dev20191202082911 If you’re using the development version of Django (aka the master branch), the docs/ directory contains all of the documentation. You can update your Git checkout be placed in docs/_build/html. 2.11.5 Differences between versions The text documentation in the master branch of the Git repository contains the “latest and greatest” changes and additions. These changes this policy: • The development documentation at https://docs.djangoproject.com/en/dev/ is from the master branch. These docs correspond to the latest feature release, plus whatever features have been added/changed

2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Other branches Tags How is Django Formed? Overview Prerequisites Pre-release tasks Preparing the master router (django.db.router). The master router is used by Django’s database operations to allocate database usage. Whenever a query needs to know which database to use, it calls the master router instance. If a hint instance wasn’t provided, or the instance doesn’t currently have database state, the master router will allocate the default database. An example Example purposes only! This example is intended

2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Other branches Tags How is Django Formed? Overview Prerequisites Pre-release tasks Preparing the master router (django.db.router). The master router is used by Django’s database operations to allocate database usage. Whenever a query needs to know which database to use, it calls the master router instance. If a hint instance wasn’t provided, or the instance doesn’t currently have database state, the master router will allocate the default database. An example Example purposes only! This example is intended

2.0 1.10 1.9 1.8 1.7 1.6 1.5 1.4 1.3 The Django source code repository High-level overview The master branch Other branches Tags How is Django Formed? Overview Prerequisites Pre-release tasks Preparing the master router (django.db.router). The master router is used by Django’s database operations to allocate database usage. Whenever a query needs to know which database to use, it calls the master router instance. If a hint instance wasn’t provided, or the instance doesn’t currently have database state, the master router will allocate the default database. An example Example purposes only! This example is intended