headers
David McNab | 1 Apr 2003 05:47
Picon
Favicon

Patch for debugger hotkeys

Attached is a modified Debugger.py file (from IDLEfork v0.9a2) which
implements hotkeys with the debugger panel.

Changes:
 - Debugger window regains focus after step/next/over/out/go commands
 - Key bindings for debugger window - windows-style:
     - F9 - Go
     - F10 - Next
     - F11 - Step
     - Shift-F11 - Out
 - source display enabled by default

In case the file attachment doesn't get through, I've put up the file
on: http://www.freenet.org.nz/misc/Debugger.py.gz

I leave it to people who are much more up-to-speed with IDLE to
incorporate these bindings into the key bindings menu.

Ahhh, now my poor sore mouse-fingers can take a break!! :))

Cheers
David
Attachment (Debugger.py.gz): application/x-gzip, 4154 bytes
Permalink | Reply | 0 comments |
headers
SourceForge.net | 1 Apr 2003 07:51
Picon
Favicon

[ idlefork-Bugs-677263 ] On W32 Can't Terminate Subprocess Not Doing IO

Bugs item #677263, was opened at 2003-01-29 20:02
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109579&aid=677263&group_id=9579

Category: None
Group: None
Status: Open
Resolution: Accepted
Priority: 7
Submitted By: Bruce Sherwood (bsherwood)
Assigned to: Kurt B. Kaiser (kbk)
Summary: On W32 Can't Terminate Subprocess Not Doing IO

Initial Comment:
With 0.9a2 it is still the case that something is very 
wrong with the run environment for VPython programs, 
at least on Windows. I run the simplest program

from visual import *
sphere()

Next I kill the graphics display window (by clicking in the 
close box), then type in the shell "2+2". I get the 
following:

Traceback (most recent call last):
  File "C:\Python23\Lib\site-packages\idleforklib\rpc.py", 
line 187, in asynccall
    self.putmessage((seq, request))
  File "C:\Python23\Lib\site-packages\idleforklib\rpc.py",
(Continue reading)

Permalink | Reply | 0 comments |
headers
Geiger Ho | 9 Apr 2003 13:05
Picon

Question on run module

Hi all,

  I use idlefork 0.9a2. My problem is that when I run my module with
other module imported altogether in my specific path, say "c:\mywork", I
get "ImportError: No module named XXX". Is there any solution for this?

  My propose solution is that I in my module, append my path to sys.path.
However, os.path.abspath() gives me that idlefork path rather than the
path my module situated. Any solution too?

  Thanks in advance.

Regards,
Geiger
Permalink | Reply | 0 comments |
headers
Heiko Schröder | 13 Apr 2003 00:08

IDLE 0.8 - severe bug?

Dear list,

I tried hard to find any information about the following bug, which I suppose 
to be a familiar one. 

I am using:

System: Linux SuSE 8.2
IDLE-Version: 0.8
Python-Version: 2.2.2
Tkinter-Version: 8.4

Problem:

Every trial to open a window -- even a help window -- in IDLE producesa 
similar Errorcode like this (tried to open Python-Documentation in IDLE):

Exception in Tkinter callback:
File /var/tmp/python-2.2.2.-build//usr/lib/python2.2/lib-tk/Tkinter.py, line 
1299 in __call__
args=apply(self.subst,args)

File /var/tmp/python-2.2.2-build//usr/lib/python2.2/lib-tk/Tkinter.py, line 
1035, in _substitute
  e.num=getint(b)

Value Error: invalid literal for int(): ??

Do you know where I will get hints to fix this bug? I am afraid that the 
Tkinter version does not match the IDLE-Version in the package which SuSE 8.2
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 13 Apr 2003 01:01
Picon
Favicon

[ idlefork-Patches-661363 ] Run multiple IDLEforks on the same machine simultanously

Patches item #661363, was opened at 2003-01-03 00:57
Message generated for change (Comment added) made by noamr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=309579&aid=661363&group_id=9579

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Noam Raphael (noamr)
Assigned to: Nobody/Anonymous (nobody)
Summary: Run multiple IDLEforks on the same machine simultanously

Initial Comment:
  Instead of defining a specific port (8833), a list of
legitimate ports is defined. When IDLE starts, it goes
over the list and tries each of the ports. When it
finds a port which is ok, it starts the subprocess.
  The list of ports which I defined is very arbitrary,
and should be reviewed.
  A more minor change, which is calling the
spawn_subprocess method only after the RPCClient class
was succesfully initialized, solves the bug that when
opening a second IDLE, an error message is displayed
but a malfunctioning shell window is displayed, and
when it's closed, the subprocess keeps on running until
the first IDLE is shut down.

----------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 13 Apr 2003 12:47
Picon
Favicon

[ idlefork-Bugs-720581 ] Restarting Shell (sometimes) causes sub-process to hang

Bugs item #720581, was opened at 2003-04-13 20:47
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109579&aid=720581&group_id=9579

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nigel Rowe (fisheggs)
Assigned to: Nobody/Anonymous (nobody)
Summary: Restarting Shell (sometimes) causes sub-process to hang

Initial Comment:
When restarting the Shell windows (Using Ctrl+F6), 
the sub-process intermittantly hangs in rpc.py with 
an unhandled exception (usually "connection reset 
by peer" or "Broken pipe") from socket.send() in 
putmessage(). 

When PyShell restarts, it interupts and shutsdown 
the sub-process, then closes the socket before 
waiting for the subprocess to exit. 

Proposed solution, reverse the order of 
self.rpcclt.close() and os.wait() in 
restart_subprocess(). 

----------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 13 Apr 2003 13:17
Picon
Favicon

[ idlefork-Bugs-720581 ] Restarting Shell (sometimes) causes sub-process to hang

Bugs item #720581, was opened at 2003-04-13 20:47
Message generated for change (Comment added) made by fisheggs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109579&aid=720581&group_id=9579

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nigel Rowe (fisheggs)
Assigned to: Nobody/Anonymous (nobody)
Summary: Restarting Shell (sometimes) causes sub-process to hang

Initial Comment:
When restarting the Shell windows (Using Ctrl+F6), 
the sub-process intermittantly hangs in rpc.py with 
an unhandled exception (usually "connection reset 
by peer" or "Broken pipe") from socket.send() in 
putmessage(). 

When PyShell restarts, it interupts and shutsdown 
the sub-process, then closes the socket before 
waiting for the subprocess to exit. 

Proposed solution, reverse the order of 
self.rpcclt.close() and os.wait() in 
restart_subprocess(). 

----------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Josh Robb | 15 Apr 2003 16:22
Gravatar

Some Pychecker Goodness...

Well. Finally I had some time this weekend to finally finish up this
code. 

Here are the results:

http://treehouse.homedns.org/~josh/pychecker.gif

http://treehouse.homedns.org/~josh/pycheck-results.gif

http://treehouse.homedns.org/~josh/pycheck-options.gif

I need to clean up the options dialogue, fix up some corner cases in the
editor error markup. Should be done this week all going well. Coming
back to programming python is such a nice feeling. <grin>

Any Feedback? The options dialogue will need some usability work. 

j.
Permalink | Reply | 1 comment |
headers
Neal Norwitz | 16 Apr 2003 03:52

Re: Some Pychecker Goodness...

On Tue, Apr 15, 2003 at 03:22:52PM +0100, Josh Robb wrote:
> Well. Finally I had some time this weekend to finally finish up this
> code. 
> 
> Here are the results:
> 
> http://treehouse.homedns.org/~josh/pychecker.gif
> 
> http://treehouse.homedns.org/~josh/pycheck-results.gif
> 
> http://treehouse.homedns.org/~josh/pycheck-options.gif
> 
> I need to clean up the options dialogue, fix up some corner cases in the
> editor error markup. Should be done this week all going well. Coming
> back to programming python is such a nice feeling. <grin>

If you hurry, you may be able to get your changes into python 2.3. :-)
2.3 beta should be coming out any week now--I'm not really sure when
though.

Hopefully, we will get idlefork moved into 2.3 also.  Not sure
of the status of idlefork either.

> Any Feedback? The options dialogue will need some usability work. 

Looks good so far.  Feel free to re-organize options if you think
they make more sense another way.  I can always change it in
pychecker too.

Neal
(Continue reading)

Permalink | Reply | 0 comments |
headers
Guido van Rossum | 16 Apr 2003 17:53
Favicon

Python 2.3b1 release

I'd like to release Python 2.3b1 around April 25.  I'd like this to
include IDLEfork instead of IDLE.  Is that feasible?  Can somebody
help with the CVS work?  (I don't need the CVS history to be
transferred, just the files.)

--Guido van Rossum (home page: http://www.python.org/~guido/)
Permalink | Reply | 5 comments |

Gmane