Thanks Graham. The issue was with the user running code that needs a python version >= python-2.7 on CentOS 5.4. Someone on the CentOS forum pointed me to the IUS Community Repo, which I didn't know about. I installed the mod_wsgi and python27 RPMs using that repository and everything is working now. It looks like this was a CentOS question more than it was a mod_wsgi question.
On Tuesday, April 14, 2015 at 6:31:08 PM UTC-4, Graham Dumpleton wrote: > > > On 14 Apr 2015, at 6:20 pm, Matt <[email protected] <javascript:>> > wrote: > > > One of my users has need for mod_wsgi on a server running CentOS 5.4. I > installed the package from RPMForge which he has found to be inadequate for > his needs. He needs for it to have been built against Python-2.7 instead of > 2.4. I'm pretty sure that this can't be done or that it at least shouldn't > be done but I'd like to get some other opinions before telling the user > this. Is there any way to install mod_wsgi that will work with python-2.7 > code on a CentOS 5.4 box? If the answer to that question is yes, would it > be worth it to put in this effort if the server in question is going to be > upgraded to CentOS 7 in a couple of weeks anyway? > > There should be no issue itself with building mod_wsgi from source code on > CentOS. If SELinux extensions are enabled that can sometimes cause issues > if the policy is very restrictive. > > What exactly are they wanting to do and do they need to be running their > web application on port 80 for the box? > > If just doing development at this point and with you upgrading the box > soon, for now they might use the pip installable mod_wsgi and simply run > mod_wsgi-express manually on port 8000. > > https://pypi.python.org/pypi/mod_wsgi > > http://blog.dscpl.com.au/2015/04/introducing-modwsgi-express.html > > http://blog.dscpl.com.au/2015/04/using-modwsgi-express-with-django.html > > http://blog.dscpl.com.au/2015/04/integrating-modwsgi-express-as-django.html > > This will allow them to build their own copy and run it out of their own > account, provided they are at least using Python virtual environments to > allow them to install into their account. > > If for some reason the main Apache installation is really old or missing > development header files, they can even pip install a special package that > will install latest Apache into their own account as well. > > When the box upgrade is done, then can sort out getting it integrated into > the main Apache installation for the system if that is necessary. > > So this might be quickest route just to get them going while get past your > upgrade. > > Have a look at this links and when have questions let me know. > > Graham -- 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.
