From: Kevin A. <al...@se...> - 2005-03-08 20:53:12
|
On Mar 8, 2005, at 10:57 AM, Thomas Heller wrote: > > I haven't looked at the install script you use, neither do I have an > up-to-date wxPython installation on my system - so I cannot try to > build > an installer myself. > > Also I have to apologize for my silence - no, the usual excuse. > > There have been several problems in the bdist_wininst installer, most > related to the nasty MS runtime dll 'conflicts' between python2.4 and > python2.3. IIRC, the problem showed up when the post-install script > was > printing something which should afterwards be displayed in the GUI. > Because of the different MS runtime dlls used, calls into these dlls > were mixed and blowing up the whole installer exe. > > I think I have fixed most of these problems in the python 2.3.5 > release, > and also in Python's 2.4 maint branch, so it would be best to build the > Pythoncard installer with Python 2.3.5 (if you want to use a released > version). > > The only problem (AFAIK) that remains is that the printed output of the > postinstall script is *not displayed* in the gui if the installer > installs for the 'wrong' Python version. At least that's some progress > - instead of crashing. > > I hope I can find time to fix bdist_wininst for the pending 2.4.1 > release that it also fixes this problem, but I'm not sure. > > Thomas > > Ok, I realized that I don't need wxPython to *build* the Pythoncard > installer. I also downloaded the 0.8.1 sources, and then built the > installer with it. For me, it installs both for Python 2.4, and Python > 2.3.5. It was build with 2.3.5 (as you can see in the distutils > version > number 1.0.4 which is shown in the first screen when the installer > runs). As mentioned before, the 'See the shortcuts installed in the > PythonCard Programs Group' is only displayed when the installer is run > for Python 2.3. Ok, not a big loss if you don't see it. > > I've uploaded the installer to > http://starship.python.net/crew/theller/PythonCard-0.8.1.win32.exe > > And finally, a suggestion: Since it is possible to have several major > Python versions (also on windows) on the same machine, it would > probably > be wise to encode the Python version number into the start menu > shortcuts as well, like 'Pythoncard for Python 2.3' or so. > > Thanks Thomas! I'll check this out and do the next build with 2.3.5. I would like to merge the install-pythoncard.py script into setup.py so there is only one file to worry about, but I don't really have a clue what is required as I'm still clueless in getting distutils to do all its magic. I'm not sure how we would go about modifying the shortcuts as suggested above either; just check the python version and modify the string before building the links I guess? ka |