Your way is better by embedding the path at configure time. Apache is
working with this. Root's config is set to load this library.
Oh and by the way, thanks for all your help. It was invaluable.
On Feb 8, 9:57 pm, Graham Dumpleton graham.dumple...@gmail.com
wrote:
On 8 February 2011 05:52,
I looked around the google code site and I found the changes in
version 4.0 page, but that doesn't contain any information on an
estimated release date. Is there a rough time frame for when it will
be released?
--
You received this message because you are subscribed to the Google Groups
modwsgi
Has anyone put together an RPM spec for building mod_wsgi 4 yet?
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from this group, send email to
Graham:
Thanks for the reply. I realize that the solution is to upgrade to
Snow Leopard, but that is not an option currently.
I certainly may have gotten lost wandering through version levels of
the different components.
I think my problems started when I tried to build the MySQLdb
connector
Can anyone explain how SCRIPT_NAME is calculated? I'm using
mod_rewrite to do per-developer cgi directories, with sometimes
amusing results in SCRIPT_NAME. I've seen in the forums that
SCRIPT_NAME is the wsgi 'mount point', but this is clearly a
simplification, because there's not always a
You may not be able to use spec file from 3.2 without some
modification unless they wildcard on source file names. This is
because mod_wsgi 4.0 in subversion trunk has multiple source files now
and not a single file.
Graham
On 10 February 2011 02:49, Clodoaldo Neto
clodoaldo.pinto.n...@gmail.com
On 10 February 2011 12:07, bc craft.br...@gmail.com wrote:
Can anyone explain how SCRIPT_NAME is calculated? I'm using
mod_rewrite to do per-developer cgi directories, with sometimes
amusing results in SCRIPT_NAME. I've seen in the forums that
SCRIPT_NAME is the wsgi 'mount point', but this is
On 10 February 2011 04:44, Michael Bartz michael.ba...@gmail.com wrote:
Graham:
Thanks for the reply. I realize that the solution is to upgrade to
Snow Leopard, but that is not an option currently.
I certainly may have gotten lost wandering through version levels of
the different
Just acknowledging that I know I haven't answered this yet. Very
little time to deal with non work stuff right now and have limited
Internet access as well. Will try and answer it over the coming
weekend.
Graham
On 8 February 2011 09:31, stipa lstipa...@gmail.com wrote:
Hi,
I am trying to
hello, i have two python versions installed on my server 2.4.3 and
2.7 , i have been running django on 2.4.3 for about 6 months and now i
want to switch to 2.7, so i installed python 2.7 by building it from
source, then i recompiled the mod_wsgi :
./configure --with-python=/usr/local/bin/python2.7
Are you loading mod_python at same time into same Apache? If you are,
remove mod_python from Apache configuration and don't use it. If
mod_python still loaded then it could be overriding what Python is
used.
Also, what do you get for:
ldd mod_wsgi.so
Graham
On 10 February 2011 17:37,
thanks for the reply,
no mod_python is not being loaded, also i ran ldd mod_wsgi.so on the
shell and it gave me:
ldd: ./mod_wsgi.so: No such file or directory
checking the error logs i found something interesting, it says :
Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.7a
On 10 February 2011 18:27, commonzenpython commonzenpyt...@gmail.com wrote:
thanks for the reply,
no mod_python is not being loaded, also i ran ldd mod_wsgi.so on the
shell and it gave me:
ldd: ./mod_wsgi.so: No such file or directory
It was assumed you would know to replace mod_wsgi.so with
13 matches
Mail list logo
