On Mon, Nov 30, 2009 at 10:48 PM, Sturla Molden <stu...@molden.no> wrote: > David Cournapeau skrev: >> If every python package starts to put its extensions (*.pyd) into a >> directory, what happens when two different packages have an extension >> with the same name (e.g. package foo has a package multiarray.pyd) ? I >> would also be really annoyed if a 3rd party extension starts polluting >> my C:\Python26. >> >> > In disutils, data_files can install DLLs where Python wants them. Just > pass 'DLLs' as path, and the rest it up to distutils. If anyone pollutes > your c:\Python26 it is distutils, not a third party extension. This is > not any different from installing other data files.
We are talking about the numpy extensions here, which are not installed through the install_data command. The problem is about how windows looks for dll with the manifest mechanism, and how to build/install extensions when the C runtime (or any other "system" dll) is not installed in the SxS cache. David _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
