I'm getting a weird error and I can't track it down. The stack trace doesn't give any clue as to the location of the error either. It's just giving me the standard urlresolvers.py ViewDoesNotExist exception. Here is the error message:
Could not import myapp.myview.views. Error was: No module named model
At first I thought I forgot to put an "s" on models somewhere in my code, but after a search of the entire codebase, that is not the case.
Here's the trackback:
File "C:\Python25\Lib\site-packages\django\core\handlers\base.py" in get_response
91. request.path_info)
File "C:\Python25\Lib\site-packages\django\core\urlresolvers.py" in resolve
216. sub_match = pattern.resolve(new_path)
File "C:\Python25\Lib\site-packages\django\core\urlresolvers.py" in resolve
216. sub_match = pattern.resolve(new_path)
File "C:\Python25\Lib\site-packages\django\core\urlresolvers.py" in resolve
216. sub_match = pattern.resolve(new_path)
File "C:\Python25\Lib\site-packages\django\core\urlresolvers.py" in resolve
123. return self.callback, args, kwargs
File "C:\Python25\Lib\site-packages\django\core\urlresolvers.py" in _get_callback
132. raise ViewDoesNotExist("Could not import %s. Error was: %s" % (mod_name, str(e)))
Exception Value: Could not import myapp.myview.views. Error was: No module named model
The DoesNotExist exception is raised when an object is not found for the given parameters of a query. Django provides a DoesNotExist exception as an attribute of each model class to identify the class of object that could not be found and to allow you to catch a particular model class with try/except .
This means that your DB is expecting that field to have a value. So when it doesn't you get an error. null. If True, Django will store empty values as NULL in the database. Default is False.
The FieldError exception is raised when there is a problem with a model field. This can happen for several reasons: A field in a model clashes with a field of the same name from an abstract base class. An infinite loop is caused by ordering.
From what you've posted, it seems like the error is in myapp.myview.views.
You already mentioned looking for misspellings of "models", which is good. You might also try asking Django to validate your models to ensure that they are properly importable (run this in your Django project root):
python manage.py validate
Beyond that, just keep following the imports in myapp.myview.views until you see something odd. You can check to see if everything is properly importable by opening a shell:
python manage.py shell
And attempting to import and/or try things from there.
Beyond that, someone may be able to assist you more if you post the full traceback. Good luck!
I have been having the same error, and I solved my problem. If you have a forms.py, ensure that all your forms fields are valid. For some reason, if your forms.py file has form field errors, then it causes this exception.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With