Bug 345951

 WFM(tm), although this is on x86_64

 What version of python/tkinter do you have?

 Does this work: python /usr/lib/python2.5/lib-tk/turtle.py

 What does your script look like?
 The above traceback looks weird, what does rpm -V tkinter say?

 The following script also works fine for me:

% cat /tmp/turt.py                      

from turtle import *
from time import *

while True:
  forward(4)
  sleep(4)

(In reply to comment #1)
>  WFM(tm), although this is on x86_64
I'm not sure about the meaning of WFM(tm)... :/

I'm using Fedora 7 on an old laptop, an IBL T23 with Linux i686 
2.6.22.9-91.fc7 
> 
>  What version of python/tkinter do you have?

rpm -qi tkinter
Version     : 2.5

> 
>  Does this work: python /usr/lib/python2.5/lib-tk/turtle.py
> 

Well, it seems to work well.

>  What does your script look like?
>  The above traceback looks weird, what does rpm -V tkinter say?

rpm -V tkinter
missing     /usr/lib/python2.5/lib-tk/turtle.pyc

I removed turtle.pyc because of a test.
I compare the Md5sum of my turtle.py with the one of another Linux user, it 
was the same but the turtle.pyc was different, on his advice, I removed it, he 
told me the .pyc wasn't really usefull.


> 
>  The following script also works fine for me:
> 
> % cat /tmp/turt.py                      
> 
> from turtle import *
> from time import *
> 
> while True:
>   forward(4)
>   sleep(4)
> 

The script :

1. #!/usr/bin/python
2. 
3. #debug script
4. 
5. from turtle import *
6. from time import *
7.  
8. while True:
9.	forward(4)
10.	sleep(4)

[lejocelyn@localhost Documents]$ python debug.py
Traceback (most recent call last):
  File "debug.py", line 5, in <module>
    from turtle import *
  File "/usr/lib/python2.5/lib-tk/turtle.py", line 6, in <module>
    by Wally Feurzeig and Seymour Papert in 1966.
NameError: name 'forward' is not defined

The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested, 
please feel free to reopen the bug report.

Thank you in advance.

Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.