I realise I'm late to this conversation, but I had to do this for my own use
recently except that I used Centos 7 and Python 3.4.
To do this for me I hacked up a bash script and put it on github:
https://github.com/marmalodak/centos_python3_django_setup/blob/master/mkenv3
I compile both Python
Tim,
Yes!
I see now what I was doing wrong; I was setting the path in the Django
settings.py (as I had found in the documentation), however, OF COURSE, that
is irrelevant because it could ever get there before mod_wsgi being aware
of where to look for libraries. Damn!
I was having the right i
I am not sure where your problem is with locale. Did you ever accomplish
recompiling mod_wsgi for Python 3.3?
This site http://www.ccdgen.com is Django 1.6, Python 3.3 and Apache 2.2 on
CentOS 6.5
I recompiled mod_wsgi as per instructions I found somewhere on the WWW.
Sorry I do not have the li
Has anybody being able to solve this problem with the locale in virtual env?
I am stuck with it for the moment.
It is just that Centos 6 + Django 1.7 (python3.x ) is a no-go?
Thanks.
On Wednesday, 7 May 2014 16:33:23 UTC+2, Guillem Liarte wrote:
>
> Timothy,
>
> Thanks you, but SELinux here doe
Timothy,
Thanks you, but SELinux here does not seem to be the issue. I tried with
enforcing/permissive/disabled and the effect is the same.
I belive the problem to be in the os path in the seetings:
---
import os
BASE_DIR = os.path.dirname(os.path.dirname(__file__))
...
...
On Tue, May 6, 2014 at 7:01 PM, Guillem Liarte <
guillem.lia...@googlemail.com> wrote:
>
>
> But I still get the locale encoding problem. Do you guys have any
> suggestions?
>
> I do not recall the exact error I had with this config (once you corrected
those you mentioned) but eventually I had to
Hello again.
The solution for the incorrect version came as a combination of both Tom's
and Brad's answer.
I could compile a mod_wsgi 3.4 with my python and I used the recommended
configuration. Now I get:
[Tue May 06 23:51:30 2014] [notice] Apache/2.2.15 (Unix) DAV/2 mod_wsgi/3.4
Python/3.3
Hello Tom,
Yes, I tried to compile wsgi with python 3.3, but I got error after error.
Instead I came back to the original quest of finding a compiled version
that works of, as it has also been indicated, to le apache know that that I
wish to use a different python.
Any specific tips when compi
It's just something that was passed down to me from a senior programmer :-)
-
Brad Pitcher
On Mon, May 5, 2014 at 2:45 PM, Guillem Liarte <
guillem.lia...@googlemail.com> wrote:
> Hello Brad,
>
> Thanks for the suggestion, I was suspecting something like that. I will
> let you know how
Hello Brad,
Thanks for the suggestion, I was suspecting something like that. I will let
you know how it goes.
Where do you find this? I Could not find anything like that in the wsgi
documentation.
Thank you,
Guillem
On Friday, 2 May 2014 16:37:35 UTC+2, Brad Pitcher wrote:
>
> What does your
What does your Apache vhost config look like? You will need to add a
WSGIDaemonProcess directive where you can specify the python path for the
virtual environment, like so:
WSGIDaemonProcess processname user=wsgi group=apache processes=1 threads=10
umask=0022 display-name=displayname
python-path=/
On Fri, May 2, 2014 at 12:11 PM, Guillem Liarte
wrote:
> Hello,
>
> I have looked through the web in several different especialised forums but I
> cannot find the way to do this properly.
>
> My aim is to have an environment to host Django applications running Centos
> 6. So far I have managed to:
Hello,
I have looked through the web in several different especialised forums but
I cannot find the way to do this properly.
My aim is to have an environment to host Django applications running Centos
6. So far I have managed to:
- Get Centos 6.5 + Ptython 3.3.2 + Django 1.6 (virtual env), run
13 matches
Mail list logo
