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 eric.araujo
Recipients cdavid, eric.araujo, exarkun, loewis, rogerbinns, tarek, techtonik, tim.golden
Date 2014-03-13.21:16:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The issue is that projects want to generate MSIs for pre- and post-release versions.  As Martin said, there is an MSI limitation here (that should be documented in distutils doc).

I see two issues with munging the version number:

1) Both Twisted 2.0+r42 and Twisted 2.0 generate twisted-2.0.msi (filename simplified for the discussion), which will surely be confusing for humans and programs.

2) Does the MSI system allow people to go from 2.0+r42 to 2.0 if each of them is in a file named twisted-2.0.msi?
Date User Action Args
2014-03-13 21:16:12eric.araujosetrecipients: + eric.araujo, loewis, exarkun, techtonik, tim.golden, tarek, cdavid, rogerbinns
2014-03-13 21:16:12eric.araujosetmessageid: <>
2014-03-13 21:16:12eric.araujolinkissue6040 messages
2014-03-13 21:16:12eric.araujocreate