This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author bethard
Recipients bethard, loewis, tarek
Date 2009-04-30.19:09:36
SpamBayes Score 3.2842885e-07
Marked as misclassified No
Message-id <1241118578.01.0.855287652423.issue5311@psf.upfronthosting.co.za>
In-reply-to
Content
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.)
History
Date User Action Args
2009-04-30 19:09:38bethardsetrecipients: + bethard, loewis, tarek
2009-04-30 19:09:38bethardsetmessageid: <1241118578.01.0.855287652423.issue5311@psf.upfronthosting.co.za>
2009-04-30 19:09:36bethardlinkissue5311 messages
2009-04-30 19:09:36bethardcreate