Re: Failed unit tests on Linux
On Wed, Mar 5, 2008 at 10:01 PM, Terry Brown [EMAIL PROTECTED] wrote: My experience shows why Linux is not exactly taking the world by storm. Heh, I think the reasons may be a little more various and complicated than that. It wasn't the source install that wiped gnome. Dis-installing python2.5, even with python2.4 around, will do the same thing. So at present I know of no way to remove python2.5 without taking gnome with it. I wonder if this is a bug in the python2.5 package... Don't worry, I'm not going to give up on Linux. Like any other OS, there are certain things that one learns not to do. Like moving or renaming anything in the Windows directory :-) Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Failed unit tests on Linux
On Mar 6, 8:19 am, Ville M. Vainio [EMAIL PROTECTED] wrote: No, you can't just remove system python installation like that, it's a feature. And a slight drawback of python being so ubiquitous today :-) Thanks for this. Saves me having to ask on comp.lang.python. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Failed unit tests on Linux
On Thu, Mar 6, 2008 at 11:10 AM, Terry Brown [EMAIL PROTECTED] wrote: First I build Tcl 8.5.1 from source ... then Tk 8.5.1 from source ... then python from source Thanks! Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Failed unit tests on Linux
On Thu, Mar 6, 2008 at 7:13 PM, Edward K. Ream [EMAIL PROTECTED] wrote: In short, all OS's are, or can be made to be, pretty much the same. That being so, Linux does indeed have real advantages for programmers. It's so cool to be able to enable thousands of packages from the package manager. Linux has real advantages for normal users as well; the most prominent probably being the unix file system approach. You can remove/rename an open file without problems. On windows, you can't even rename a *directory* when one file under it is open somewhere. Quite often one has to log off windows to accomplish something simple such as renaming that directory. Not to mention the flexibily of symlinks that can cross file systems (as opposed to NTFS junctions), the fragility of drive letter based file system (with various SUBST hacks) etc. -- Ville M. Vainio - vivainio.googlepages.com blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio' --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Failed unit tests on Linux
On Mar 5, 10:20 am, Edward K. Ream [EMAIL PROTECTED] wrote: There appears to be a serious problem on my Linux install. I should mention that the failures occur with the latest revision (56) of the bzr trunk. This revision contains the proposed code for Leo 4.4.8 b1. Any further revisions between now and b1 will be very minor. All unit tests pass on XP. The failures I have described only happen on Linux. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Failed unit tests on Linux
On Wed, 5 Mar 2008 08:26:04 -0800 (PST) Edward K. Ream [EMAIL PROTECTED] wrote: I suspect recent Python/Tkinter bugs are causing the X crash. Really, this kind of crash should never arise with normal Python bugs. Oddly enough I have a similar issue. I'm getting seg. faults and sometimes STACK: Stack after current is in use when trying to load non-trivial leo files with my python 2.5.1 install which is supposed to be using Tk 8.4.x. However gdb reports the crash is occurring in /usr/local/lib/libTk8.5.1 (approx.) so I think my installation of Tk 8.5.1 had tainted the system default install of tkinter somehow. Using my python 2.5.2 install which is supposed to be using Tk 8.5.1 everything works perfectly, in fact better than perfect, it's anti-aliased :-) Cheers -Terry --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Failed unit tests on Linux
On Mar 5, 10:55 am, Terry Brown [EMAIL PROTECTED] wrote: On Wed, 5 Mar 2008 08:26:04 -0800 (PST) Edward K. Ream [EMAIL PROTECTED] wrote: I suspect recent Python/Tkinter bugs are causing the X crash. Really, this kind of crash should never arise with normal Python bugs. Oddly enough I have a similar issue. I'm getting seg. faults and sometimes STACK: Stack after current is in use when trying to load non-trivial leo files with my python 2.5.1 install which is supposed to be using Tk 8.4.x. However gdb reports the crash is occurring in /usr/local/lib/libTk8.5.1 (approx.) so I think my installation of Tk 8.5.1 had tainted the system default install of tkinter somehow. Using my python 2.5.2 install which is supposed to be using Tk 8.5.1 everything works perfectly, in fact better than perfect, it's anti-aliased :-) I ran into an adventure when I tried to upgrade to Python 2.5.2 on Ubuntu. First, I downloaded Python2.5.2, and followed the install directions, which was a source install. All seemed to go well, but Python2.5.2 couldn't find Tkinter. So I de-installed Python. Same problem. So I de-installed all Python versions. Adventure! Glade got de-installed. Bye bye windows! Happily, apt-get still existed, so I used it to re-install glade. After a reboot the windows reappeared :-) I then used the synaptic package manager to reinstall all my Python stuff. But Python2.5 *still* can't find tkinter. However, Python2.4 works, so I can run Leo. Any idea how I can install Tk so Python2.5 can find it? Imo, there are enough problems with Python2.5 so that I feel justified in releasing Leo 4.4.8 b1 tomorrow, regardless of the Python follies on Ubuntu. If there are, in fact, real problems with Leo, we may as well fix them after b1. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: Failed unit tests on Linux
On Mar 5, 2:38 pm, Edward K. Ream [EMAIL PROTECTED] wrote: On Mar 5, 10:55 am, Terry Brown [EMAIL PROTECTED] wrote: Any idea how I can install Tk so Python2.5 can find it? Doing whereis python produced a long list, so I did the following: python signs on as 2.5.2, so we are using the recently installed python, the python that I compiled from sources. Presumably the make process did not find Tk.. Found the install directory by doing import sys print sys.executable It was installed in /usr/local/bin The Synaptic package manager did *not* know about this. I suppose this makes sense: I didn't install it from a debian package. BTW, I considered removing python2.5 from the package manager, but this would have de-installed lots of stuff, and now I know that would not be A Good Thing (tm). Anyway, I go to /usr/local/bin and do sudo rm py* to erase the locally- installed stuff. BTW, the original sources were saved in the /tmp directory, and they went away after the reboot. So even if python setup.py uninstall would have worked, it would have required me to download python again! Perhaps I should have done that... Anyway(2) python now signs on as 2.5.1, so I have effectively trashed the (presumably improperly made) python 2.5.2. Now Leo can load with Python 2.5.1, so I am back where I started, wiser, and perhaps even happier. OTOH, uninstall by erasing files as su makes me more than a little uneasy... My experience shows why Linux is not exactly taking the world by storm. The install/uninstall business usually works, but when it fails it fails catastrophically. Newbies would never have known to do apt-get, and would never have guessed that gnome was the windows manager. And even someone with my experience is still in the dark about how to *totally* uninstall python without trashing the entire system! On another note, the present unit tests look like they are failing on python 2.4 also. One approach will be to run tests of various versions of Leo until I discover which version may have caused the failed tests. But there is no need to delay Leo 4.4.8 on this account. All in all, a fairly amusing day :-) Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
