I've done so, thanks for pointing the discussion. In the meantime, I've just patched distutils/msvc9compiler.py so that it neither embed nor create a manifest assembly. This way, I'll be sure that the assembly information would be fetched from the main python (or python-based) binaries (i.e. pythonX.dll). That may be a very strong prerequisites in some cases, but never in my very particular case. Eloi Christoph Gohlke wrote:
The most popular/simple way to deal with the VC90.CRT dependency issue is to have the user install the runtime redistributable on their system. If you don't want to put that burden on the user, which I understand, you have to make adjustments to the assembly manifests. This is not unofficial or unsupported. It is a bug in Python that it embeds the assemblyIdentity for VC90.CRT in all extensions build with distutils/msvc9compiler.py. In fact, the *.pyd distributed with Python 2.6.3+ don't have that problem. Maybe you can raise your concerns about future compatibility at http://bugs.python.org/issue4120.
Christoph
On 11/30/2009 1:11 AM, Eloi Gaudry wrote:
Christoph, thanks for pointing this discussion. That's a perfect match.
If the workaround provided offers a solution to the current redistribution issue, I'm wondering if it will still be the case when an update to the assembly check function will be activated/implemented (within Windows). The manifest edition (removing the "assemblyIdentity" tag) doesn't seem to be a popular/official/supported way of dealing with the whole runtime libraries issue. Don't you think ?
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
-- Eloi Gaudry Free Field Technologies Axis Park Louvain-la-Neuve Rue Emile Francqui, 1 B-1435 Mont-Saint Guibert BELGIUM Company Phone: +32 10 487 959 Company Fax: +32 10 454 626