[Django] #22573: ImportError: No module named header

28 views
Skip to first unread message

Django

unread,
May 4, 2014, 1:24:08 PM5/4/14
to django-...@googlegroups.com
#22573: ImportError: No module named header
---------------------------------+--------------------
Reporter: Haikson | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.6
Severity: Release blocker | Keywords: 1.6.4
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------
Traceback (most recent call last):
File "./wsgi.py", line 13, in <module>
from django.core.wsgi import get_wsgi_application
File "/srv/env/vsevseti/lib/python2.7/site-
packages/django/core/wsgi.py", line 1, in <module>
from django.core.handlers.wsgi import WSGIHandler
File "/srv/env/vsevseti/lib/python2.7/site-
packages/django/core/handlers/wsgi.py", line 9, in <module>
from django import http
File "/srv/env/vsevseti/lib/python2.7/site-
packages/django/http/__init__.py", line 4, in <module>
from django.http.response import (HttpResponse, StreamingHttpResponse,
File "/srv/env/vsevseti/lib/python2.7/site-
packages/django/http/response.py", line 6, in <module>
from email.header import Header
ImportError: No module named header
unable to load app 0 (mountpoint='') (callable not found or import error)
*** no app loaded. going in full dynamic mode ***
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 24205)
spawned uWSGI worker 1 (pid: 24212, cores: 1)
--- no python application found, check your startup logs for errors ---

--
Ticket URL: <https://code.djangoproject.com/ticket/22573>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
May 4, 2014, 2:13:20 PM5/4/14
to django-...@googlegroups.com
#22573: ImportError: No module named header
---------------------------------+--------------------------------------
Reporter: Haikson | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.6
Severity: Release blocker | Resolution: invalid

Keywords: 1.6.4 | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by timo):

* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0


Comment:

I don't think this is an issue with Django. I guess you might have another
module named `email` on your Python path that's taking precedence over the
Python stdlib version.

https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels

--
Ticket URL: <https://code.djangoproject.com/ticket/22573#comment:1>

Reply all
Reply to author
Forward
0 new messages