The issue was as you suspected: homebrew's mod_wsgi was built for python
2.7. In addition,
pip install mod_wsgi
resulted in it being built for 2.7 as well. As a solution, since pip is
bundled with the python install, I had to execute
pip3 install mod_wsgi
and update the LoadModule path to
/usr/local/lib/python3.4/site-packages/mod_wsgi-4.4.9-py3.4-macosx-10.10-x86_64.egg/mod_wsgi/server/mod_wsgi-py34.so
in the Apache conf file. Now, the site is running on the Python 3.4
virtualenv.
Given that this is an easy mistake to make, particularly given the
proliferation of Python 2.7.x installed along with 3.x on the same
machines, it would make sense for the install documentation to reflect the
differences in installations for 2.7.x & 3.x environments.
Thanks for the hint to get this issue fixed!
Jason
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
