patch to make msvccompiler.py work with vs 2005(MSVC8)

[weck]

BPO	1447
Nosy	@loewis, @tiran
Files	msvccompiler.py.diff

^{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 2007-11-15.18:25:25.182>
created_at = <Date 2007-11-15.14:21:35.141>
labels = ['build', 'expert-installation']
title = 'patch to make msvccompiler.py work with vs 2005(MSVC8)'
updated_at = <Date 2007-11-15.18:25:25.158>
user = 'https://bugs.python.org/weck'

bugs.python.org fields:

activity = <Date 2007-11-15.18:25:25.158>
actor = 'loewis'
assignee = 'none'
closed = True
closed_date = <Date 2007-11-15.18:25:25.182>
closer = 'loewis'
components = ['Installation']
creation = <Date 2007-11-15.14:21:35.141>
creator = 'weck'
dependencies = []
files = ['8752']
hgrepos = []
issue_num = 1447
keywords = ['patch']
message_count = 3.0
messages = ['57530', '57536', '57542']
nosy_count = 3.0
nosy_names = ['loewis', 'christian.heimes', 'weck']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue1447'
versions = ['Python 2.6', 'Python 3.0']

[weck]

It seems that the directory information of MSVC8 *just* can be got from
environment variable instead of registry.

This patch make me compile pywin32 with MSVC8(VS 2005).

[tiran]

I've checked your patch. It's not enough to move to VS 2005 as the
default compiler. People expect python setup.py to work w/o opening a VS
2005 Command Prompt.

[loewis]

tiran is correct. distutils should work without having to invoke a VS
build environment. Relying on that environment would have worked way
back to VC6 and earlier, but it would reduce the ease of use of distutils.

Rejecting the patch.