Re: Code run from IDLE but not via double-clicking on its *.py
- From: "n00m" <n00m@xxxxxxxx>
- Date: 31 Aug 2005 05:14:32 -0700
Funnily but I still can't get the code working... WITHOUT IDLE.
I think it's because of "import thread" line. Seems something
wrong with "opening" this module. In IDLE it works OK.
.
- Follow-Ups:
- Re: Code run from IDLE but not via double-clicking on its *.py
- From: Steve Holden
- Re: Code run from IDLE but not via double-clicking on its *.py
- From: Richie Hindle
- Re: Code run from IDLE but not via double-clicking on its *.py
- References:
- Code run from IDLE but not via double-clicking on its *.py
- From: n00m
- Re: Code run from IDLE but not via double-clicking on its *.py
- From: n00m
- Re: Code run from IDLE but not via double-clicking on its *.py
- From: Richie Hindle
- Re: Code run from IDLE but not via double-clicking on its *.py
- From: n00m
- Code run from IDLE but not via double-clicking on its *.py
- Prev by Date: Re: Yielding a chain of values
- Next by Date: Re: OpenSource documentation problems
- Previous by thread: Re: Code run from IDLE but not via double-clicking on its *.py
- Next by thread: Re: Code run from IDLE but not via double-clicking on its *.py
- Index(es):
