Ubuntu is a suitable choice. The Django team apparently uses it. For starters, Ubuntu has old and new versions of python. 2.5 is available in Hardy LTS, and 2.6 is in the newest stable release.
Secondly, django itself is available in the repositories, as python-django. This might seem pointless as people generally deploy Django from SVN, but it does mean there's a place to report integration problems and documented dependencies and suggestions.
Specifically, use the WSGIPythonHome directive to tell mod_wsgi that your Python is actually in a different location.
If this doesn't work, then make sure you are no longer loading mod_python into same Apache if you had been previously. Perform a complete stop and start of Apache, not just a reload, for good measure to ensure that mod_python no longer hanging around. The mod_python module cant be used at the same time because it will take precedence in initialising Python and will use what ever it is compiled against, which could well be different to mod_wsgi. Normally this mixing will cause a crash, but feasible it may carry along a little bit before deciding to croak it.
Best Answer
Look for
/usr/lib/apache2/modules/mod_wsgi.so*, at least on ubuntu I have:If you change the symlink, you change the default mod_wsgi.
An alternative is to look in
/etc/apache2/mods-enabled/wsgi.load, for me that's just one line:If you point that at one of those
mod_wsgi.so-2.xfiles, you've changed the default version.