[issue4091] python dll not installed in windows system directory

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Committed as r66958, r66959, and r66960. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> _

[issue4091] python dll not installed in windows system directory

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: r61109 became obsolete when I added support for the merge module; here is a patch that fixes this. An installer demonstrating the change is available from http://www.dcl.hpi.uni-potsdam.de/home/loewis/u/python-2.7.14165.msi -- keywo

[issue4091] python dll not installed in windows system directory

Changes by Mark Hammond <[EMAIL PROTECTED]>: -- nosy: +mhammond ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue4091] python dll not installed in windows system directory

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > (And I thought that manifests and side-by-side assemblies were > supposed to solve the "DLL hell") I'm now convinced that they make things worse, to the degree that certain deployments that used to work cannot be longer made to work (e.g.

[issue4091] python dll not installed in windows system directory

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The following lines in msi.py seem to be the cause of the change: #dlldir = PyDirectory(db, cab, root, srcdir, "DLLDIR", ".") #install python30.dll into root dir for now dlldir = root They were added by r61109: Bundle msvcr90.

[issue4091] python dll not installed in windows system directory

New submission from Thomas Heller <[EMAIL PROTECTED]>: Python 2.6 final and Python 3.0 rc1 do NOT install the python dlls into the windows system directory, even when installing 'for all users' and with admin rights. This causes problems with COM objects implemented in Python. Observed on Windo