Re: Tracking a bad import

2009-07-02 Thread Andrew Fong
Ignoring thread hijacking there and responding to the OP. The next time you have an import error, try using the -v option, like this: python -v manage.py syncdb That'll print every module being imported as it's being imported -- it might help identify what's missing. Alternatively, use pdb (htt

Re: Tracking a bad import

2009-07-02 Thread Xiong Chiamiov
On Jul 1, 9:15 pm, Chhouk Voeun wrote: > i want to use map url (http:\\localhost:8080\main).oh i use window Did you read the tutorial? None of your url regexes look anything like /main/. And why did you hijack someone else's thread that was about a completely different topic? --~--~-~-

Re: Tracking a bad import

2009-07-01 Thread Chhouk Voeun
i want to use map url (http:\\localhost:8080\main).oh i use window --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscrib

Re: Tracking a bad import

2009-07-01 Thread Chhouk Voeun
i use window and i can start page .the sample code follow:# Copyright 2008 Google Inc. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licen

Re: Tracking a bad import

2009-07-01 Thread goodwinb
Fixed it by reinstalling all of my packages. On Jul 1, 8:48 pm, goodwinb wrote: > I am setting up a server and when I run manage.py syncdb I get the > error 'cannot import name pre_delete'.  How can I get more trace > information about where the bad pre_delete is? > > Python 2.6; Django 1.1-beta

Re: Tracking a bad import

2009-07-01 Thread Chhouk Voeun
Page not found (404) Request Method: GET Request URL: http://localhost:8080/main/ Using the URLconf defined in pollango.urls, Django tried these URL patterns, in this order: 1. ^$ 2. ^create/$ 3. ^poll/(?P[^\.^/]+)/$ 4. ^poll/(?P[^\.^/]+)/results/$ The current URL, /main/, didn't

Tracking a bad import

2009-07-01 Thread goodwinb
I am setting up a server and when I run manage.py syncdb I get the error 'cannot import name pre_delete'. How can I get more trace information about where the bad pre_delete is? Python 2.6; Django 1.1-beta; using comments, markdown, statlib --~--~-~--~~~---~--~~