Thank you for the info. That's how I've been doing it but assumed something wasn't right as it wasn't working and I keep getting errors. I think I've ruled out python as the problem Need to start looking at the mod_wsgi and Apache setup.
I have another post regarding Apache errors I will get back to, is there a way to close this topic? On Tuesday, November 6, 2012 11:14:53 AM UTC-5, Nikolas Stevenson-Molnar wrote: > > Whenever you run a Django command (e.g., startapp, runserver), just use > the full path to your Python 2.7 interpreter. For example: > > $ /opt/python2.7/bin/python manage.py runserver 80 > > Similarly, if you're installing packages via pip or easy_install: > > $ /opt/python2.7/bin/pip install some_package > $ /opt/python2.7/bin/easy_install some_package > > _Nik > > On 11/6/2012 7:09 AM, Bestrafung wrote: > > I have been running into this problem for a long while trying to setup > > my first Django project and I keep coming back to this problem. I am > > relatively new when it come to Linux, I'm learning but still have a > > long way to go. I am using CentOS 5.8 cPanel which comes with Python > > 2.4. Following instructions I found online for setting up Django with > > cPanel I compiled/installed Python 2.7 from source to /opt/python2.7 > > and set an alias (alias python="/opt/python2.7/bin/python") in the > > root and user's .bash_profile and python 2.7 launches as expected when > > you use the python command. Every time I try to start a project or > > work with it however the system default python 2.4 keeps popping up. I > > think this may be the single cause of all of my issues. When starting > > a project I have just appended the python command to make sure it > > started with the correct version. I believe that once the project is > > started it isn't working because everything is still trying to use > > 2.4. Is there a way to make Django use my 2.7 install instead of 2.4 > > without breaking the system by making the 2.7 system default? > > -- > > You received this message because you are subscribed to the Google > > Groups "Django users" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/django-users/-/WqpZIEJqalcJ. > > To post to this group, send email to > > [email protected]<javascript:>. > > > To unsubscribe from this group, send email to > > [email protected] <javascript:>. > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/OVUWdCah_fwJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
