An earlier message seemed to suggest that using the SVN source version of Ulipad would fix this issue. Have you tried that yet?
On Mon, Jul 27, 2009 at 4:57 PM, Dick Moores <[email protected]> wrote: > > On Mon, Jul 27, 2009 at 13:19, Werner F. Bruhin<[email protected]> wrote: > > > > James Matthews wrote: > >> > >> That means that 2.5.1 is your default python installation (ie, when you > >> double-click on a .py file the 2.5.1 interpreter runs it). > > > > Py 2.5.1 is pretty outdated, would suggest to use 2.5.4 as the default > > Python. > >> > >> You need to make 2.6.2 your default python installation > > > > I frankly would not do this yet, there are too many moduls/libraries not > yet > > 2.6/3.0 compatible - i.e. it is a bit too bleeding edge for me, > especially > > as the default. > > > > this seems to do double do things, i.e. call pythonw.exe and .pyw > > E:\Python26>pythonw.exe E:\Programs\Ulipad3.7\Ulipad.pyw > > > > What happens if you do this? > > E:\Python26>pythonw.exe E:\Programs\Ulipad3.7\Ulipad.py > > Nothing: > C:\Documents and Settings\Riley>e: > E:\>cd python26 > E:\Python26>pythonw.exe E:\Programs\Ulipad3.7\Ulipad.py > E:\Python26> > > > And above is done from a Windows command prompt and not a short cut to > > ensure that you see any error output (as Dear Bill thinks it is nice to > > suppress errors when one uses a short cut). > > > > Is "Programs" your Windows program file folder? > > No, that's C:\Program Files > > If yes, you should not keep > > Python type folders underneath this, might still work in XP but will bite > > you in Vista and Win7. Folders where one needs to write to (i.e. Python > > needs to create .pyc files) should not be under the "Program Files" > folder, > > I put most of my Python modules libraries underneath the python path > (most > > of them are anyhow Python Version specific), i.e. into > > pythonxx\lib\site-packages or into something like \dev\ or ....... > > > > Werner > > Dick >
