msiexec not creating msvcr90.dll with python -2.7.6.msi

[dykesk]

BPO	22497
Nosy	@zware, @zooba

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2020-03-20.17:53:25.913>
created_at = <Date 2014-09-25.16:36:49.252>
labels = ['OS-windows']
title = 'msiexec not creating msvcr90.dll with python -2.7.6.msi'
updated_at = <Date 2020-03-20.17:53:25.913>
user = 'https://bugs.python.org/dykesk'

bugs.python.org fields:

activity = <Date 2020-03-20.17:53:25.913>
actor = 'steve.dower'
assignee = 'none'
closed = True
closed_date = <Date 2020-03-20.17:53:25.913>
closer = 'steve.dower'
components = ['Windows']
creation = <Date 2014-09-25.16:36:49.252>
creator = 'dykesk'
dependencies = []
files = []
hgrepos = []
issue_num = 22497
keywords = []
message_count = 2.0
messages = ['227550', '227565']
nosy_count = 3.0
nosy_names = ['zach.ware', 'steve.dower', 'dykesk']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue22497'
versions = ['Python 2.7']

[dykesk]

This is a new issue meant to resurrect bpo-5459. When Python 2.7.x (and 2.6.x before that) are installed for all users, then 'msvcr90.dll' is not created in the installation directory. It does if you install for a single user. However, many Windows users install Python for all users by default. This causes problems later when trying to install software that combines any sort of C or Fortran code.

[zooba]

When you install for all users, the msvcr90.dll is also installed for all users and should appear in your System32/SysWOW64 directory.

What sort of problems are you facing? Compiled DLLs/pyds that are loaded into a running Python process should reuse the already loaded DLL (and Python won't have started if it couldn't resolve the CRT DLL).