[Python-3000] [Python-Dev] 2.6.1 and 3.0

[Giovanni Bajo]

On Wed, 19 Nov 2008 20:40:38 +0100, Martin v. Löwis wrote:

> The tricky part really is when it breaks (which it does more often than
> not), in which case you need to understand msi.py, for which you need to
> understand MSI. IMO, the Microsoft is excellent (in being fairly
> precise), but the learning curve is high. The mechanical part of it can
> is completely automated - we produce daily MSI files in a buildbot slave
> (which may or may not work - I haven't checked in a while)

I always wondered why it was necessary to write msi.py in the first 
place. Maintaining it is surely a big effort and requires understanding 
of a dark library which a few people have (IMO it's a much higher effort 
than setting up automated tests in a bunch of VM, which you said is "not 
worth it").

There are plenty of MSI installer generator programs, and Python's needs 
do not seem so weird to require a custom MSI generator. I'm sure the 
Python Software Foundation would easily get a free license of one of the 
good commercial MSI installer generators.

In short: if msi.py and the fact it breaks is part of the issue here, 
it's very easy to solve in my opinion.
-- 
Giovanni Bajo
Develer S.r.l.
http://www.develer.com