Steven Bethard <steven.beth...@gmail.com> added the comment: Ok, that was actually easier than I thought it would be. The new patch introduces properties for each Python version (e.g. TARGETDIR2.4, PYTHON.MACHINE.2.4, etc.), and disables and hides the features for any Python versions that aren't found in the registry.
The one remaining issue: What should we do about Python installations that are missing the appropriate keys in the registry? I imagine this could happen if, say, you build Python from source. My first thought was to add an "Other Python Installation" Feature that is disabled (but visible) by default, and allow the path for that Feature to be filled in by hand. Does that make sense? ---------- Added file: http://bugs.python.org/file13841/bdist_msi.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5311> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
