Steven Bethard <steven.beth...@gmail.com> added the comment: I'm still stuck on getting the right name to show up in ARP.
Another problem: it seems like we have to update the ProductCode at runtime as well - otherwise, you can only have one module installed for all the versions of Python you have on your machine. But if we generate a new GUID at runtime, how do we make sure that the GUID for moduleXXX + Python 2.6 is the same every time (as it should be for the MSI to recognize when a product is being removed, reinstalled, etc.) Thoughts? Is there a way to deterministically generate a GUID for each Python version? (Note that it doesn't make sense to do this ahead of time - an installer created for Python 3.1 should work with Python 3.2 as well.) ---------- _______________________________________ 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
