Éric Araujo added the comment: 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? ---------- assignee: tarek -> components: +Distutils -Distutils2 nosy: +exarkun versions: +Python 3.5 -3rd party _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6040> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
