Sunday, February 28, 2016

Re: Error running Django tutorial

Yes, the server was started.  Here are the contents of the command window, including after trying to go to the website.


C:\Data\Django_Code\FirstApp\mysite>python manage.py runserver
Performing system checks...

System check identified no issues (0 silenced).

You have unapplied migrations; your app may not work properly until they are applied.
Run 'python manage.py migrate' to apply them.
February 28, 2016 - 21:05:58
Django version 1.9.2, using settings 'mysite.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CTRL-BREAK.
Not Found: /polls/
[28/Feb/2016 21:06:30] "GET /polls/ HTTP/1.1" 404 1921
Not Found: /favicon.ico
[28/Feb/2016 21:06:31] "GET /favicon.ico HTTP/1.1" 404 1936


On Saturday, February 27, 2016 at 1:50:39 PM UTC-6, Mike Kipling wrote:
I am working through the Django tutorial Writing your first Django app, part 1.
I am using Windows 10, python 3.5.1 and Django 1.9.2 .
 
In the Write your first view section: 
    after writing the polls/views.py and polls/urls.py files,
    and modifying the manage/urls.py file,
    and starting the server,
 
    When I go to http://localhost:8000/polls/ in the browser I get the following error:

Page not found (404)

Request Method: GET
Request URL: http://localhost:8000/polls/

Using the URLconf defined in mysite.urls, Django tried these URL patterns, in this order:

  1. ^admin/

The current URL, polls/, didn't match any of these.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/33ec29f2-9800-44b5-af10-1f1a2a5d9713%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment