#17298 closed Bug (invalid)
Error: No module named filterspecs
Reported by: | Keats | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Release blocker | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Hi,
the stable version 1.3.1 is bugged for testing with multidb when we try to test :
it was patched in https://code.djangoproject.com/ticket/16828
but trunk is bugged also but for everything :
$python manage.py test
Error: No module named filterspecs
$python manage.py runserver
Error: No module named filterspecs
thanx
Change History (3)
comment:1 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 13 years ago
ok founded the bug
from django.contrib.admin.filterspecs import FilterSpec
no longer exists
thanx
comment:3 by , 12 years ago
Shouldn't this throw a proper traceback, instead of showing a generic error, forcing you to hunt through your code (and all external libraries) that may be attempting this import.
This looks like an error in your application's code: it imports a module that doesn't exist, or with the wrong path.
If you need support on this issue, I suggest asking on the #django IRC channel on Freenode or on the django-users mailing list, since it isn't a bug in Django itself. If Django had a bug that caused both
manage.py runserver
andmanage.py test
to fail unconditionally, we'd know it :)