Eryk Sun added the comment:
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
----------
nosy: +eryksun
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue31103>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
