[mod_python] problems installing on OS 10.5

>
>
> This is because you are trying to use MacPorts version of Python, or
> one you installed yourself, which doesn't include all architectures as
> part of the Python installation. That or you are using version of GCC
> which didn't come with MacOS X and it doesn't support generation of 64
> bit binaries properly. This is covered in the mod_wsgi documentation.
>

Well -- I guess I'm using the GCC that came with Xcode.    The python I'm
using the is the build of 2.5.2 that I got as a binary from www.python.org,
the frameork install that's gets installed in:

/Library/Frameworks/Python.framework/Versions/Current/bin/python

I've never had a problem building 64 binaries before ...


If it is CGI, then see about turning it into a WSGI application.


So, you're saying that the object of not having to have a new python
interprerter opened for every request is achieved properly if I use wsgi?


Thanks very much for this information below, though I think I need to
understand the wsgi model sort of from scratch ...

Dan

The
> main difference is that the request environment is passed as a
> parameter into your application rather than it being in os.environ.
> When generating a response, you need to return it from the
> application, rather that just using 'print' to produce it. Another
> thing that may catch you is that since now persistent if using
> mod_wsgi, you need to ensure you don't preserve temporary working
> state in variables that could be incorrectly accessed by subsequent
> request. Otherwise usually not too hard to convert a CGI application
> to WSGI.
>
> Finally, if your scripts are multithread safe, you would want to
> ensure that you use mod_wsgi daemon mode with only a single threaded
> process.
>
> Graham
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mm_cfg_has_not_been_edited_to_set_host_domains/pipermail/mod_python/attachments/20090309/f366c536/attachment-0001.html