[pywin32-bugs] [ pywin32-Bugs-900551 ] Build 200 doesn't set registry Modules\py* entries

[SourceForge.net <no...@so...>]

Bugs item #900551, was opened at 2004-02-19 19:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=900551&group_id=78018

Category: win32
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Eric Promislow (ericp)
Assigned to: Nobody/Anonymous (nobody)
Summary: Build 200 doesn't set registry Modules\py* entries

Initial Comment:
Visual Python depends on the presence of the 
pythoncom extensions, and checks for the correct
registry entries, based on the version of Python, as an 
MSI Launch Condition.  This is because I use pythoncom 
as part of the registration process, and it's better to 
check for its presence in advance than to fall flat on my 
face in the CustomAction section.

I noticed with build 200 that the registry entries
HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.
3\Modules\{pythoncom,Pythonwin,pywintypes} aren't 
created.  If this is deliberate, could I please have them 
back?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=900551&group_id=78018