Hi all, I just wanted to mention that dropping VS2008 support is a very > serious issue for anyone working with Python. All major Python > versions currently available (2.6, 2.7 and 3.2) are built with VS2008. > Python extension modules (and any of their dependencies which share C > standard library bits like malloc and free) have to be built with the > same compiler in order to avoid mixing C runtimes. Right now h5py > (and I would expect, PyTables) is built against a version of HDF5 > compiled with VS2008 for this reason. In particular, if you allocate > any memory on the Python side which is freed by HDF5 (or vice versa) > you have to use the same compiler. > > Ah, I hadn't thought of that. I'll mention that to the appropriate people.
Does anyone know when the Python folks plan to upgrade to VS2010? VS2008 is four years old and is now the n-2 version. That's getting a little long in the tooth. > In practical terms, what this means for us is that the version of HDF5 > shipping with h5py for Python 2.6, 2.7 and 3.2 will be frozen at > 1.8.10. In particular, HDF5 1.10 will also be unsupported on all > currently available Python platforms, unless we can figure out a way > around the C runtime issue. > > There is no way around the C runtime issue that I know of. Do people who use h5py, etc. use our binaries (which I assume) or do they build HDF5 via CMake? > Would the HDF Group accept bug reports/patches from the community to > fix issues with VS2008 as they come up? > I would assume so, but I don't think we've had a lot of problems with VS-specific issues in HDF5. Usually Windows bugs apply to all versions of Visual Studio and Windows. Cheers, Dana
_______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
