You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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='https://github.com/tarekziade'closed_at=<Date2008-12-30.23:11:44.828>created_at=<Date2008-12-19.21:33:08.278>labels= ['type-bug', 'library']
title='[PATCH] msvc9compiler raises IOError when no compiler found instead of DistutilsError'updated_at=<Date2008-12-30.23:11:44.800>user='https://github.com/pjenvey'
Python 2.6's new msvc9compiler misbehaves when it can't find a compiler
(actually a utility of the missing compiler) in its query_vcvarsall() --
it raises an IOError instead of a typical distutils error
build tools expect a consistent set of potential exceptions from the
compiler suites, such as CCompilerError, DistutilsExecError,
DistutilsPlatformError, etc. Distributions like simplejson, Genshi, etc.
look for these errors when compiling their optional C extension speedups
as an indication that there's no compiler, and to fallback to their pure
python counterparts
An IOError in this case just doesn't make sense
This patch changes them to DistutilsExecErrors. Maybe it should be
DistutilsPlatformError -- whatever, just not IOError
I agree with the patch, except that DistutilsPlatformError seems more
appropriate - this function is called when the compiler object is
configured, before it is used to actually compile files.
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: