Thanks. That did the trick.
Mike Driscoll wrote:
> On Feb 12, 2:18 pm, "W. Watson" <[EMAIL PROTECTED]> wrote:
>> After simply trying to write a program with help(MakeQTE), a module, and
>> having it fail with socket errors, I decided to restart IDLE, thinking I
...
>
> I sometimes get this messag
En Tue, 12 Feb 2008 18:18:20 -0200, W. Watson <[EMAIL PROTECTED]>
escribió:
> After simply trying to write a program with help(MakeQTE), a module, and
> having it fail with socket errors, I decided to restart IDLE, thinking I
> knew the cause. I'm now getting msgs like: "IDLE's subprocess didn't
On Feb 12, 2:18 pm, "W. Watson" <[EMAIL PROTECTED]> wrote:
> After simply trying to write a program with help(MakeQTE), a module, and
> having it fail with socket errors, I decided to restart IDLE, thinking I
> knew the cause. I'm now getting msgs like: "IDLE's subprocess didn't make
> connection.
After simply trying to write a program with help(MakeQTE), a module, and
having it fail with socket errors, I decided to restart IDLE, thinking I
knew the cause. I'm now getting msgs like: "IDLE's subprocess didn't make
connection. ... firewall may be blocking the connection." I doubt the FW
co
