#17298: Error: No module named filterspecs
---------------------------------+--------------------------------------
Reporter: Keats | Owner: nobody
Type: Bug | Status: closed
Component: Core (Other) | Version: SVN
Severity: Release blocker | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by aaugustin):
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
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` and `manage.py test` to fail unconditionally, we'd know it :)
--
Ticket URL: <https://code.djangoproject.com/ticket/17298#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
