[mod_python] transhandler setup?

IR labs wrote:
> Sorry for a late reply.
> 
> I feel really silly for my problem, *really* silly. (almost too silly to 
> let you all know ...)
> After trying all different things in the httpd.conf and not seeing any 
> noticeable result, I started thinking it could be having to do with 
> apache not reading it after I issued "sudo apachectl restart". And then 
> I realized that, after I upgraded to apache 2, to make mod_python work 
> decently, I forgot to also change the path to /usr/local/apache2/bin in 
> my .profile. DUH... So every time I tried to made a change to apache2's 
> httpd.conf and "restarted" I restarted apache 1, ... well, zero points 
> for dirk and no desert for a week. :-(

It's an easy mistake to make, with a simple solution:

1. Always prepend root's $PATH with /usr/local/sbin:/usr/local/bin (and 
just /usr/local/bin for ordinary users). I typically make sure this is 
done globally in /etc/profile, which works for some shells, but others 
may require edits to other files. However you accomplish this, I 
consider it quite sane. For experimental installs of applications, use 
your own ~/bin and *append* that to your path.

2. Use an init script if your system supports it. You can either change 
the stock one or create a new one for your particular version. For 
example, on Slackware Linux, the startup script is /etc/rc.d/rc.httpd. 
Since I install my own apache 2.x without uninstalling Slack's 1.3x 
version, I create /etc/rc.d/rc.apache, and everything is harmonious.