Steven Bethard <steven.beth...@gmail.com> added the comment: Ok, I've been chatting with folks on microsoft.public.platformsdk.msi, and I think the right approach here is to define a Feature for each version of Python. Each Feature would install the exact same files, but to a different Python directory.
One of the nice things about this approach would be that you could install a module for multiple Python versions all at the same time. It also should avoid the need for a VBScript or C-based CustomAction - we should be able to do everything with the database tables. One of the downsides is that we'll have to hard-code in all possible versions of Python. My current plan is just to declare all versions as 2.0, 2.1, ..., 3.9. That should be good enough for a while, but at some point this will have to get updated to work with Python 4.0. ;-) I'll post back here when I've made some progress on this. ---------- _______________________________________ 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
