Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#17298 closed Bug (invalid)

Error: No module named filterspecs

Reported by: Keats Owned by: nobody
Component: Core (Other) Version: master
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



the stable version 1.3.1 is bugged for testing with multidb when we try to test :
it was patched in

but trunk is bugged also but for everything :
$python test
Error: No module named filterspecs

$python runserver
Error: No module named filterspecs


Change History (3)

comment:1 Changed 5 years ago by Aymeric Augustin

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Resolution: invalid
Status: newclosed

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 runserver and test to fail unconditionally, we'd know it :)

comment:2 Changed 5 years ago by anonymous

ok founded the bug

from django.contrib.admin.filterspecs import FilterSpec

no longer exists


comment:3 Changed 4 years ago by anonymous

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.

Note: See TracTickets for help on using tickets.
Back to Top