The sphinx tool chain now creates the htmlhelp files as python30a5.* but
the MSI installer packages expects pydoc.chm. Either msi.py or the doc
tool chain must be altered.

By the way Martin:
Should the RM set snapshot to 0 in Tools/msi/msi.py before tagging a
release?

This is now fixed in r62949.

I don't quite understood why this had the priority "high" - it just
worked fine the way it was - you just have to manually rename the result
file.

In any case, I'd appreciate if the file name scheme stays as-is unless a
change is mutually agreed upon.

As for setting snapshot to 0: absolutely no. This is the privilege of
whoever builds the official releases. Even somebody checking out a
release tag should not automatically build a release version of the MSI,
as it would then be questionable which of them is the official one (they
would use the same product code). Setting snapshot to 0 is a privilege
of the release engineer.

Martin: I'm sorry that this created work for you; but I had assumed that
distributing the new docs created so much work anyways that this
wouldn't matter too much :)

> Martin: I'm sorry that this created work for you; but I had assumed that
> distributing the new docs created so much work anyways that this
> wouldn't matter too much :)

The remaining issue is to get Tools/buildbot/buildmsi.bat to name the
generated hhp file correctly.

Regards,
Martin

Is there a way to run the tree Python?

> Is there a way to run the tree Python?

Currently, that should be possible, as the documentation is
built after Python. However, in the long term, cross-compilation
needs to be considered (to AMD64 on an x86 machine); then you
can't run the tree python on the build machine.

I would prefer if there was a makefile target that invoked
hhc, from "%ProgramFiles%\HTML Help Workshop\hhc.exe" directly.
It's guaranteed that make (i.e. cygwin make) will find a Python
interpreter (i.e. cygwin python2.5). Then buidmsi could just
invoke that target directly after htmlhelp.