Message213470
| 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 |
<1394745372.41.0.909435184358.issue6040@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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? |
|