2008/10/24 Nimrod A. Abing <[EMAIL PROTECTED]>:
>
> On Fri, Oct 24, 2008 at 11:42 AM, Graham Dumpleton
> <[EMAIL PROTECTED]> wrote:
>>
>> 2008/10/24 Graham Dumpleton <[EMAIL PROTECTED]>:
>>> I have created the issue:
>>>
>>>  http://code.google.com/p/modwsgi/issues/detail?id=114
>>>
>>> as a placeholder for any requests to document simple recipes related
>>> to Apache configuration and mod_wsgi.
>>>
>>> I have added a few of my own already. If you have others you would
>>> like to see, then add them against that issue.
>>>
>>> Please only put one request per comment rather than grouping many in
>>> one. That way easier for me to pick them out.
>>>
>>> As I got a copy of Apache Cookbook from my Amazon Wish List yesterday,
>>> will possibly have lots more when I read through book and find
>>> examples which might have some special relevance to mod_wsgi usage.
>>
>> In respect of:
>>
>>  http://code.google.com/p/modwsgi/issues/detail?id=114#c5
>>
>> Does:
>>
>>  http://code.google.com/p/modwsgi/wiki/VirtualEnvironments
>>
>> not cover WSGIPythonHome and WSGIPythonPath adequately?
>
> It does but it mainly concerns virtualenv and is not really in the
> "simple recipe" form. I was thinking more of a scenario when you have
> 2 Python installations, one packaged by your Linux distro and the
> other built from source and installed in /usr/local/ and you built
> mod_wsgi using the Python installed in /usr/local. How would you use
> WSGIPythonHome and WSGIPythonPath to set up your mod_wsgi to use the
> one in /usr/local/.

Okay. This was actually one of the scenarios I specifically want to
cover in a revised Django guide. Specifically, using last tarball
release in site-packages from main installation for one instance and
then a SVN checkout for another instance. This scenario seems to come
up quite a bit in Django land.

Graham

> As for WSGIPythonExecutable, I have one deployment which was still
> stuck at Apache 1.2 so I had to use mod_wsgi 1.5. For some reason
> WSGIPythonHome and WSGIPythonPath would not work so I had to use
> WSGIPythonExecutable. I can't really recall what I was doing wrong at
> the time (was under time pressure). I don't have access to that server
> anymore and I'm just glad it's out of my hands now.
> --
> Best Regards,
> Nimrod A. Abing
>
> W http://arsenic.ph/
> W http://preownedcar.com/
> W http://preownedbike.com/
> W http://abing.gotdns.com/
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
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/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to