Re: [Tutor] Help debuging a small program

2005-02-22 Thread Kent Johnson
Mark Kels wrote: On Mon, 21 Feb 2005 13:21:35 -0500, Kent Johnson <[EMAIL PROTECTED]> wrote: How far does it get? How do you know? I would put some debug print statements in. Also you should call sk.close() in the else clause of scan(). Finally, I don't think you will see any output in the result

Re: [Tutor] Help debuging a small program

2005-02-22 Thread Martin Walsh
Mark Kels wrote: On Mon, 21 Feb 2005 13:21:35 -0500, Kent Johnson <[EMAIL PROTECTED]> wrote: How far does it get? How do you know? I would put some debug print statements in. Also you should call sk.close() in the else clause of scan(). Finally, I don't think you will see any output in the resul

Re: [Tutor] Help debuging a small program

2005-02-22 Thread Mark Kels
On Mon, 21 Feb 2005 13:21:35 -0500, Kent Johnson <[EMAIL PROTECTED]> wrote: > How far does it get? How do you know? > > I would put some debug print statements in. Also you should call sk.close() > in the else clause of > scan(). Finally, I don't think you will see any output in the result window

Re: [Tutor] Help debuging a small program

2005-02-21 Thread Kent Johnson
Mark Kels wrote: Hi list ! Here is a small port scanner I made to practice sockets and GUI programming ( WARNING: the program crash when scan button is clicked): How far does it get? How do you know? I would put some debug print statements in. Also you should call sk.close() in the else clause of

[Tutor] Help debuging a small program

2005-02-21 Thread Mark Kels
Hi list ! Here is a small port scanner I made to practice sockets and GUI programming ( WARNING: the program crash when scan button is clicked): #--Imports-- from Tkinter import * import socket #--The result GUI window function- def result(): global result_t #I