Fix broken unregistration of 64bit type libraries (second attempt) #678
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
UnRegisterTypeLib
function currently always assume 32bit type libraries (SYS_WIN32
) if called without explicitsyskind
argument. This is currently the case whenUnRegisterTypeLib
is called implicitly fromcomtypes.server.register.UseCommandLine
, since the_reg_typelib_
field only contains the first 3libID
,wVerMajor
andwVerMinor
arguments.Propose to fix the problem by updating the hardcoding to
SYS_WIN64
for 64bit Python andSYS_WIN32
for 32bit Python installations. This ensures that existing 32bit COM servers continue to function on 32bit Python installations.