Add support for Python 2.6

[jjr8]

To make GeoEco compatible with ArcGIS 10 (see #411), we must start building GeoEco for Python 2.6. Specific work items not already done include:

• Install and configure the Microsoft Visual Studio 2008 compiler, which is what the Python team used to build Python 2.6. [DONE; r542 and MGET 0.8a9]

• Build rpy 2.5.0 - 2.11.1 for Python 2.6. [DONE; r542 and MGET 0.8a9]

• GeoEco's HDF tools do not work anymore because they invoke hdp.exe which links at load time to zlib1.dll, and the zlib1.dll from  http://vbkto.dyndns.org/sdk/release-1500-dev.zip was apparently compiled with Visual Studio 2008, causing it to link in turn to msvcr90.dll. For a process to load that DLL, it must have a Windows manifest specifying the dependency. But the hdp.exe that we have does not have an internal manifest, causing it to fail at run time when it tries to load zlib1.dll which tries to load msvcr90.dll. I think the best solution, for now, is to replace GDAL's zlib1.dll with the one available on the zlib website, which was compiled using an older compiler that yields a dependency on msvcrt.dll does not create this manifest problem. [DONE; r542 and MGET 0.8a9]

• Figure out how to get the MATLAB-based code to compile with VS 2008. Currently, we use MATLAB 2007b, which only supported VS 2003 and 2005. I checked the MATLAB forums and someone there described how to add support for VS 2008. But there is the further problem of how to get MATLAB to programmatically switch from one to the other. When we build GeoEco for Python 2.4 and 2.5 we want to continue to use VS 2003, but when we build for Python 2.6, we want to use 2008.

• Build assimilated pyproj module for Python 2.6 or eliminate the dependency on it. [DONE; r542 and MGET 0.8a9; NOT YET TESTED]

• Update the Installation Instructions to include Python 2.6. [DONE; r718 and MGET 0.8a22]

[jjr8]

Basic support for Python 2.6 was implemented in r542, released in MGET 0.8a9. I am leaving the ticket open until all work items are completed.

[jjr8]

All of these have been done for a while. I probably should have closed this bug months ago.