On 11/02/2010 05:24, Mark Jones wrote: [... problems building from tools/msi ...]
I sympathise. I went through similar hoops last year, merely to be able to do it. I think I'm right in saying that very few people are bothered enough to package their own MSI on windows because the (probably very few) developers who have a need to run bleeding-edge Python, eg to test out patches or whatever, can simply run from <checkout>\pcbuild\python_d.exe or whatever. And everyone else simply runs the MSI provided on python.org. I'm fairly sure I'm right in saying that it's Martin von L who builds the MSIs for python.org and if I haven't done it before I'd like to offer him a vote of thanks for having done and for continuing to do this. The tools/msi is used by him to do those builds and does make certain assumptions. One, in particular, is that you have an *existing* copy of some recent Python running somewhere. (I use python25, I think). Altho' it might be nice to be able to bootstrap, in practice it isn't a problem. For interest's sake I offer my make-snapshots area which I use to build trunk or branches for Python 2.x / 3.x when I have the change: http://svn.tjg.org.uk/make-snapshots Feel free to look at least to see what I'm doing. I think I didn't bother with Tix (I don't use Tkinter) so thanks for providing some input on that; I may well go back and retrofit. TJG -- http://mail.python.org/mailman/listinfo/python-list
