Author chrullrich
Recipients chrullrich, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2016-10-25.19:49:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1477424947.52.0.871422001177.issue25166@psf.upfronthosting.co.za>
In-reply-to
Content
This bug has been open for over a year and two subsequent releases, and its planned resolution depends on a change to WiX. The related WiX bug (see comment above) is scheduled to be implemented in WiX 4.0, which has no prospective release date. According to <https://github.com/wixtoolset/issues/milestone/4>, only 27 percent of the issues currently planned for this release are resolved.

In my opinion, this is an important bug that cannot wait indefinitely.

Ceterum censeo (yes, there had to be one): This is particularly true when considering that a (relatively) simple fix exists that can be done by the Python project alone, with no external dependencies. I am referring, of course, to dropping the burn bundle entirely and shipping a single MSI package again, rather than 43 (!) of them (across x86 and amd64) with an average of ~190 and a median of 8 (eight) installed files per package in 3.5.2, counting pip.
History
Date User Action Args
2016-10-25 19:49:07chrullrichsetrecipients: + chrullrich, paul.moore, tim.golden, zach.ware, eryksun, steve.dower
2016-10-25 19:49:07chrullrichsetmessageid: <1477424947.52.0.871422001177.issue25166@psf.upfronthosting.co.za>
2016-10-25 19:49:07chrullrichlinkissue25166 messages
2016-10-25 19:49:06chrullrichcreate