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 eryksun
Recipients Markus Kramer, damon-atkins, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-08-02.22:41:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501713708.83.0.127891568124.issue31103@psf.upfronthosting.co.za>
In-reply-to
Content
The docs [1] are clear that this property must be of the form major.minor.build. It can include at least one additional field, which the installer ignores. The major and minor version numbers can be up to 255, and the build number can be up to 65535. Python's ProductVersion property complies with this:

    db = msilib.OpenDatabase('core.msi', msilib.MSIDBOPEN_READONLY)
    v = db.OpenView("select * from Property where Property='ProductVersion'")
    v.Execute(None)
    r = v.Fetch()

    >>> r.GetString(2)
    '3.6.2150.0'

It would be unorthodox to use the build version field for Python's micro release version number. I don't see why it's really important since micro releases are ABI compatible for in-place upgrades.

[1]: https://msdn.microsoft.com/en-us/library/windows/desktop/aa370859
History
Date User Action Args
2017-08-02 22:41:48eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, damon-atkins, Markus Kramer
2017-08-02 22:41:48eryksunsetmessageid: <1501713708.83.0.127891568124.issue31103@psf.upfronthosting.co.za>
2017-08-02 22:41:48eryksunlinkissue31103 messages
2017-08-02 22:41:48eryksuncreate