From S.E.Latham at rl.ac.uk Thu May 6 07:10:53 2004 From: S.E.Latham at rl.ac.uk (Latham, SE (Sue) ) Date: Thu May 6 07:11:01 2004 Subject: [Idle-dev] some requirements Message-ID: <49F73BEED865D3119F8700902773C9F9035F4304@exchange09.rl.ac.uk> I've just tried idle for debugging and I think it needs a few more features before I would use it regularly for this purpose. Some suggestions:- - Conditional breakpoints. - Ability to inspect and change variables/ object values as you go along by right-clicking on the item in the source window. - Ability to pass arguments when running a script. - Close source windows when modules have been exited (or ability to choose which module source windows to always have open). - also liked Al Schapira's suggestion of entering and evaluating an expression whenever you like If any of these things can already be done, please let me know how (I couldn't see any mention in the documentation or help). Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/idle-dev/attachments/20040506/d88c8880/attachment.html From S.E.Latham at rl.ac.uk Thu May 6 07:25:35 2004 From: S.E.Latham at rl.ac.uk (Latham, SE (Sue) ) Date: Thu May 6 07:25:40 2004 Subject: [Idle-dev] Linux "dialog" utility Message-ID: <49F73BEED865D3119F8700902773C9F9035F4306@exchange09.rl.ac.uk> Just tried using the Linux "dialog" utility whilst within idle - this really messed it up! Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/idle-dev/attachments/20040506/97b3cf18/attachment.html From kbk at shore.net Sat May 8 10:00:11 2004 From: kbk at shore.net (Kurt B. Kaiser) Date: Sat May 8 10:00:24 2004 Subject: [Idle-dev] Linux "dialog" utility In-Reply-To: <49F73BEED865D3119F8700902773C9F9035F4306@exchange09.rl.ac.uk> (SE Latham's message of "Thu, 6 May 2004 12:25:35 +0100") References: <49F73BEED865D3119F8700902773C9F9035F4306@exchange09.rl.ac.uk> Message-ID: "Latham, SE (Sue) " writes: > Just tried using the Linux "dialog" utility whilst within idle - > this really messed it up! Using a curses-based display in X is problematic. You might try Xdialog, and maybe take a look at the xdialog Python wrapper for Xdialog: www.chrisarndt.de/en/software/python -- KBK From markus.ingvarsson at lugn.nu Sun May 9 08:44:30 2004 From: markus.ingvarsson at lugn.nu (Markus Ingvarsson) Date: Sun May 9 08:44:36 2004 Subject: [Idle-dev] Python 2.3 IDLE is randomly freezing. Message-ID: <20040509124430.GA1412@neutron> I'm having the same problems as Martin and I can't see any response from him, so I'll jump in :-) >> What happens is that after 10 minutes or so of typing in the idle >> editor window the application freezaes and stops repainting. There is >> no traceback output on the terminal. >> >> How do I go about debugging this? I tried to instantiate an >> EditorWindow in the debugger but it appears to require quite a bit >> of environment. Any help would be greatly appreciated. > > Could be difficult. From what you say, it's happening while you > are entering code, not executing it. That's a critical difference. > Is there any pattern to the failures? Are you entering a lot of > text? For me, it always happens when I'm typing "fast", mostly when deleting large chunks of text. It doesn't matter if it's in PyShell or while editing a file. > Keep running apt-get upgrade. Try Sarge, if possible. I was running the version in testing but upgraded and hoped the bug would be fixed.. > Try running IDLE with the -n switch so it starts without the > subprocess. If you still see the problem, it's likely Sid has > lost his mind again. Still hangs. > Otherwise, if the problem disappears there may be an issue with > subprocess communications. > > In rpc.py, near the end, you will find two debugging switches: > debugging = False > > Set these to True and restart IDLE. This will generate a lot of trace > information relative to communications between the GUI and the > subprocess. Note that because of threading and multiprocess issues, > the traces are not strictly in time sequence order. But they have > sequence numbers to help with the analysis. Changed debugging to True in RPCClient and RPCHandler, a lot of output is produced but nothing special when it hangs though. > What's the Debian Bug # ? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245408 -- Markus Ingvarsson From sunet2000 at yahoo.com Sun May 9 17:20:19 2004 From: sunet2000 at yahoo.com (Martin Cameron) Date: Sun May 9 17:20:23 2004 Subject: [Idle-dev] Python 2.3 IDLE is randomly freezing. Message-ID: <20040509212019.573.qmail@web41204.mail.yahoo.com> Yep, I'm still here! I've not been doing much python recently but the problem is still there. With -n the app is not so prone to crashing, but still does after an hour or so for me. I've got a few ipc traces but they don't seem to correlate at all. Not good! Regards, Martin __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover From kbk at shore.net Tue May 18 00:44:23 2004 From: kbk at shore.net (Kurt B. Kaiser) Date: Tue May 18 00:44:27 2004 Subject: [Idle-dev] Python 2.3 IDLE is randomly freezing. In-Reply-To: <20040509124430.GA1412@neutron> (Markus Ingvarsson's message of "Sun, 9 May 2004 14:44:30 +0200") References: <20040509124430.GA1412@neutron> Message-ID: <87n04673a0.fsf@hydra.localdomain> Markus Ingvarsson writes: > For me, it always happens when I'm typing "fast", mostly when deleting large > chunks of text. It doesn't matter if it's in PyShell or while editing a file. > >> Keep running apt-get upgrade. Try Sarge, if possible. > > I was running the version in testing but upgraded and hoped the bug would be fixed.. > >> Try running IDLE with the -n switch so it starts without the >> subprocess. If you still see the problem, it's likely Sid has >> lost his mind again. > > Still hangs. So it's not the subprocess or subprocess communication. [...] > Changed debugging to True in RPCClient and RPCHandler, a lot of output > is produced but nothing special when it hangs though. No sense dealing with that if you can reproduce the problem w/o using the subprocess. Sounds like a Tk problem in the Sid environment. Try setting up a Tk text widget without using IDLE and see if you can reproduce the problem. -- KBK From markus.ingvarsson at lugn.nu Wed May 19 13:26:51 2004 From: markus.ingvarsson at lugn.nu (Markus Ingvarsson) Date: Wed May 19 13:26:56 2004 Subject: [Idle-dev] Python 2.3 IDLE is randomly freezing. In-Reply-To: <87n04673a0.fsf@hydra.localdomain> References: <20040509124430.GA1412@neutron> <87n04673a0.fsf@hydra.localdomain> Message-ID: <20040519172651.GA2509@neutron> > > Changed debugging to True in RPCClient and RPCHandler, a lot of output > > is produced but nothing special when it hangs though. > > No sense dealing with that if you can reproduce the problem w/o using the > subprocess. Yes, I realized that just after I had sent the mail, what was I thinking? :-) > Sounds like a Tk problem in the Sid environment. Try setting up a Tk text widget > without using IDLE and see if you can reproduce the problem. I created a window with just a textbox in it and pressed a key for quite some time, erased and typing randomly, it didn't hang. IDLE usually hangs after a few seconds if I do this. I say _usually_ because I've been trying different ways to provoke the bug. If I open a new window (no syntax highlighting), I can type for all I care without it hanging. But in PyShell or when editing a file (syntax highlighting), it hangs sooner or later - especially when holding a key pressed for a while. -- Markus Ingvarsson From Jason.Hopkins at med.ge.com Tue May 25 11:20:17 2004 From: Jason.Hopkins at med.ge.com (Hopkins, Jason (MED, GEMS-IT)) Date: Tue May 25 11:20:27 2004 Subject: [Idle-dev] IDLE Backspace not working correctly in Win2000 Message-ID: I am running IDLE 1.0.2 & Python 2.3.3 in Win2000 and XP. On my XP box I don't have any problems, but in Win2000 when I hit backspace or when I hit Enter to start a new line a small square box appears. When I hit backspace the letter to the left becomes a box and then I'm set back to the same position I was when I started. Looks like this: >>> backspace >>> backspac The hex is 08, so it looks like a backspace, but I don't know why it doesn't work. Return creates a new line then puts a box on that line. It's hex is 0d, so it looks like a newline, again, I don't understand why this works on XP, but not on my 2k box. Thanks, Jason