John Zelle wrote:
>
>VPython runs a GTK (I think) event loop in a separate thread, to stay
>interactive in IDLE.
>
I believe this is true on Unix, but that VPython uses a native OpenGL
capable window on Windows.
It has seemed to me that VPython event loop handling is problematic.
The IDLE ev
Scott David Daniels wrote:
> Kirby Urner wrote:
>
>
>>Speculation on my part. On target?
>
>
> Sounds right, but I really haven't investigated beyond learning how to
> get back to the point where I can experiment with TkInter interactively.
> There is so much more learning possible with the
Scott David Daniels schrieb:
> Andy Judkis wrote:
> ...
>
>>Livewires graphics routines behave differently under Python 2.4.1 than they
>>...
> you can start Idle with the "separate process" feature disabled by
> changing the idle startup from something like: "python ...idle.pyw"
> to something
Kirby Urner wrote:
> Speculation on my part. On target?
Sounds right, but I really haven't investigated beyond learning how to
get back to the point where I can experiment with TkInter interactively.
There is so much more learning possible with the immediate feedback,
that it is worth (to me) th
> Hope this helps and is clear enough. Happy instructing.
>
> --Scott David Daniels
> [EMAIL PROTECTED]
We also ended up using this -n switch when I taught Python to home schoolers
at FreeGeek that time (Rita's class).[1]
I think because the one Python executable was in some shared bin on the
Andy Judkis wrote:
...
> Livewires graphics routines behave differently under Python 2.4.1 than they
> do under 2.2.3. Under 2.4.1, in IDLE, if I interactively run
from livewires import *
begin_graphics()
circle(100,100,50, filled=True)
circle(300,300,70)
end_graphics()
> then
Hello,
I have a very nuts-and-bolts question for you folks. I have found that the
Livewires graphics routines behave differently under Python 2.4.1 than they
do under 2.2.3. Specifically, under the former, in IDLE, if I interactively
run
>>> from livewires import *
>>> begin_graphics()
>>> ci
