Closed GoogleCodeExporter closed 8 years ago
This is not the mailing list and there is no broad audience here to answer your
question. The mailing list is at:
http://groups.google.com/group/modwsgi
Can only suggest two things and if they don't work then try the mailing list or
even StackOverflow site,
referencing this issue so people know what you have been told already.
First thing is to know that Apache service runs as a special user on Windows.
That user must have read access to
Python code files and loadable modules plus dependent DLLs. If it doesn't it
will not be able to find them.
Second is that as Apache runs as service, it does use your user environment.
Thus if required DLLs are not
installed in main system DLL library directory or elsewhere then Apache will
not be able to find them and you
may get a DLL load error.
So, verify that Apache service user has read access to everything it needs and
secondly that DLLs required by
matplotlib are in location on standard DLL search paths.
Original comment by Graham.Dumpleton@gmail.com
on 18 Nov 2009 at 9:02
That should read:
"""Second is that as Apache runs as service, it does NOT use your user
environment."""
Original comment by Graham.Dumpleton@gmail.com
on 18 Nov 2009 at 9:05
Dear Graham.Dumpleton,
Many many thanks for your rapid response.
I have struggle for solve this problem all day.
I think the problem is the DLL file, also I find a useful reference:
http://old.nabble.com/matplotlib._path-failed-on-windows-build-for-Python-2.6-td
22963286.html
Besides, I also write a article about "How to Integrate Django with Apache
--榛果和阿帕契的整合--"(writed by mandarin),
http://docs.google.com/View?id=dfrfs8nb_1490cwwfjrkn
In this article, I use mod_wsgi to do the job.
mod_wsgi is excellent!!
Original comment by t5318...@gmail.com
on 18 Nov 2009 at 9:39
If anyone has this problem, this can be solved by using FastCGI.
I have used FastCGI to run my Django application and matplotlib.
I will still to find out what cause the "DLL load error".
Original comment by t5318...@gmail.com
on 19 Nov 2009 at 3:45
Presumed to be environment issue with user so closing.
Original comment by Graham.Dumpleton@gmail.com
on 22 Nov 2009 at 3:03
Original issue reported on code.google.com by
t5318...@gmail.com
on 18 Nov 2009 at 7:15