To be dealt with after change freeze. Two pieces to this puzzle:

1. Currently in fas and bodhi and probably other httpd config files for running under mod_wsgi we have
   {{{
   WSGIPythonOptimze 2
   }}}

This is unnecessary and could potentially break future code that wants to read docstrings. It's a better idea to set this to {{{WSGIPythonOptimize 1}}}. This change should have nearly no impact on us.

1. Something is preventing us from hotfixing the fas servers. On May 21, I tried to hotfix the fas server on fas1 and fas2 by doing this:

{{{

change user.py in /usr/lib/python2.4/site-packages/fas

cd /usr/lib/python2.4/site-packages/fas
patch -p2 < ~/fas-email.patch
rm user.pyc user.pyo
/etc/init.d/httpd graceful
}}}

This restarted the fas processes but the new server threads were unable to find the user.py file. Instead, they kept looking for user.pyo and only user.pyo. Documented behaviour for the python interpreter would be to fallback on the .py file and try to use that both to startup and to create a user.pyo file. Running:
{{{
sudo python -O -c 'import compileall; compileall.compile_dir(".", '2', "/", 1)
}}}

compiled a pyo file from user.py and then we were able to continue. WSGIPythonOptimize might be the cause of this as well. I'm leaning against that, though, as we're running WSGIPythonOptimize 2 on fas1.stg and that seems to work.