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 loewis
Recipients cdavid, eric.araujo, exarkun, loewis, rogerbinns, tarek, techtonik, tim.golden
Date 2014-03-14.01:41:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As for 2): I believe that bdist_msi doesn't support upgrade installations currently, anyway. To support this, the UpgradeCode property would have to be specified. As it stands, multiple versions of the same PyPI package result in multiple separate installations (potentially overwriting each other's files).

It would be possible to automatically derive an UpgradeCode from the metadata, however, we would then still need to define what versions replace each other, and what versions can be installed side-by-side.

In any case, the name of the MSI file is irrelevant (AFAIK). They could be named the same or differently - what matters to Windows is the package code, the product code, and the upgrade code. The ProductVersion matters for the UI, and to determine whether something is an upgrade. See
Date User Action Args
2014-03-14 01:41:32loewissetrecipients: + loewis, exarkun, techtonik, tim.golden, tarek, cdavid, eric.araujo, rogerbinns
2014-03-14 01:41:32loewissetmessageid: <>
2014-03-14 01:41:31loewislinkissue6040 messages
2014-03-14 01:41:31loewiscreate