[issue6040] bdist_msi does not deal with pre-release version

Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If y

[issue6040] bdist_msi does not deal with pre-release version

Martin v. Löwis added the comment: 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 installatio

[issue6040] bdist_msi does not deal with pre-release version

É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 Twis

[issue6040] bdist_msi does not deal with pre-release version

anatoly techtonik added the comment: Feel free to copy this report for a clear user story - http://twistedmatrix.com/trac/ticket/5024 -- ___ Python tracker ___ _

[issue6040] bdist_msi does not deal with pre-release version

Éric Araujo added the comment: Well, this is the bug tracker for the stdlib. We have first to define clearly what the bug is, then find how to fix it in packaging (the name of distutils2 merged into 3.3), then decide whether to backport it to distutils. Half-tested recipes to work-around th

[issue6040] bdist_msi does not deal with pre-release version

anatoly techtonik added the comment: What for? IIUC, it won't be fixed in distutils anyway. -- ___ Python tracker ___ ___ Python-bugs-

[issue6040] bdist_msi does not deal with pre-release version

Éric Araujo added the comment: To keep this focused, we should first try to make a test and patch for the stdlib, then discuss a recipe to work around the bug in unfixed versions. -- ___ Python tracker ___

[issue6040] bdist_msi does not deal with pre-release version

anatoly techtonik added the comment: All right. The ultimate solution: {{{ # Imports for converting version to MSI format for bdist_msi from distutils.command.bdist_msi import bdist_msi import inspect import types ... class bdist_msi_patch_version(bdist_msi): """ MSI builder requires ver

[issue6040] bdist_msi does not deal with pre-release version

anatoly techtonik added the comment: s/while/whole/ Sorry. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6040] bdist_msi does not deal with pre-release version

anatoly techtonik added the comment: The above workaround still doesn't isolate version modification to bdist_msi command, because bdist_msi is calling `build` and `install` targets before doing its own stuff. Any ideas how to override version for MSI without copying while `bdist_msi` conten

[issue6040] bdist_msi does not deal with pre-release version

anatoly techtonik added the comment: Wrong code. The last line in the bdist_msi_version_hack override should be: self.distribution.metadata.version = saved -- ___ Python tracker _

[issue6040] bdist_msi does not deal with pre-release version

anatoly techtonik added the comment: Metadata can be automatically figured out using regexp matching like ^\d+(\.\d+){2,3}, but for explicit handling there should be should some callback or msi-specific version property in metadata. In the end it is pretty logical if binary distribution proce

[issue6040] bdist_msi does not deal with pre-release version

anatoly techtonik added the comment: Is there any workaround we can use in setup.py to set correct version for build_msi subcommand only? -- nosy: +techtonik ___ Python tracker

[issue6040] bdist_msi does not deal with pre-release version

Changes by Éric Araujo : -- components: +Distutils2 -Distutils nosy: +eric.araujo versions: +3rd party -Python 3.2 ___ Python tracker ___ _

[issue6040] bdist_msi does not deal with pre-release version

Changes by Tim Golden : -- nosy: +tim.golden ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue6040] bdist_msi does not deal with pre-release version

Changes by Terry J. Reedy : -- assignee: -> tarek components: +Distutils nosy: +tarek type: -> feature request versions: +Python 3.2 -Python 2.4, Python 2.5, Python 2.6 ___ Python tracker _

[issue6040] bdist_msi does not deal with pre-release version

Martin v. Löwis added the comment: The problem is that the version number goes into the MSI ProductVersion property, which MUST be numeric, or else Windows will refuse to install the package. So this is not just an arbitrary choice (at least not by bdist_msi). I'm not sure how a strictly nume

[issue6040] bdist_msi does not deal with pre-release version

Roger Binns added the comment: This issue is highly annoying. The ultimate cause is the msi code using the StrictVersion class to get the version number. StrictVersion is documented to be constrained to numerical dot separated versions, and there doesn't appear to be a way of providing that.

[issue6040] bdist_msi does not deal with pre-release version

New submission from Cournapeau David : If bdist_msi is used on a package which has a non released version (defined from StrictVersion), it refuses to build the package. The code for the bdist_msi mentions that pre-release is not supported. Knowing nothing about msi, I don't know what shall be don