Bad news:
I ran the 2.5 turtle.py through the 2to3 refactorer but the
result would not run in 3.1, some kind of type mismatch between
ints and NoneType. So I set it aside.
Good news:
I tracked down the actual cause of the image discrepencies in my
report.
http://www.mensanator.com/mensanator/Py
On Aug 5, 7:49 pm, Gregor Lingl wrote:
> Mensanator schrieb:
>
> > On Aug 5, 5:31 pm, Mensanator wrote:
> >> I fixed this to produce the actual image I'm looking
> >> for instead of that stupid black square. All I did was
> >> use up() & dowm() in place of penup(), pendown() and
> >> replace dot(
Mensanator schrieb:
On Aug 5, 5:31 pm, Mensanator wrote:
I fixed this to produce the actual image I'm looking
for instead of that stupid black square. All I did was
use up() & dowm() in place of penup(), pendown() and
replace dot(2) with forward(1).
I'll be posting a followup report later.
On Aug 5, 5:31 pm, Mensanator wrote:
> I fixed this to produce the actual image I'm looking
> for instead of that stupid black square. All I did was
> use up() & dowm() in place of penup(), pendown() and
> replace dot(2) with forward(1).
>
> I'll be posting a followup report later.
>
http://www.m
I fixed this to produce the actual image I'm looking
for instead of that stupid black square. All I did was
use up() & dowm() in place of penup(), pendown() and
replace dot(2) with forward(1).
I'll be posting a followup report later.
import gmpy
## (even) hi|
##|
##
On Aug 5, 12:56 pm, Gregor Lingl wrote:
> Mensanator schrieb:
>
>
>
>
>
> >> It didn't form 2.5 to 2.6 (at least not intentionally). But with the
> >> indroduction of the TurtleScreen class and the Screen class/object
> >> (singleton) a few of the turtle methods were also implemented as screen
> >
On Aug 5, 3:08 pm, Ethan Furman wrote:
> Mensanator wrote:
>
>
>
>
>
>
>
>
>
> > What does this mean?
>
> import turtle
> tooter = turtle.Turtle()
> *tooter*.tracer
>
> > Traceback (most recent call last):
> > File "", line 1, in
> > tooter.tracer
> > AttributeError: 'Turtle' o
Mensanator wrote:
What does this mean?
import turtle
tooter = turtle.Turtle()
*tooter*.tracer
Traceback (most recent call last):
File "", line 1, in
tooter.tracer
AttributeError: 'Turtle' object has no attribute 'tracer'
tooter.hideturtle()
tooter.speed('fast')
turtle.update()
*
On 5 Aug., 21:31, Mensanator wrote:
>
> >>> import turtle
> >>> tooter = turtle.Turtle()
> >>> tooter.tracer
>
> Traceback (most recent call last):
> File "", line 1, in
> tooter.tracer
> AttributeError: 'Turtle' object has no attribute 'tracer'>>>
> tooter.hideturtle()
> >>> tooter.speed(
On Aug 5, 2:19 am, Steven D'Aprano wrote:
> On Wed, 5 Aug 2009 03:49 pm Mensanator wrote:
>
> > In 3.1, tracing is now a screen attribute, not a turtle atribute.
> > I have no idea why
>
> > tooter = turtle.Turtle()
> > tooter.tracer(False)
>
> > doesn't give me an error (I thought silent erro
Mensanator schrieb:
It didn't form 2.5 to 2.6 (at least not intentionally). But with the
indroduction of the TurtleScreen class and the Screen class/object
(singleton) a few of the turtle methods were also implemented as screen
methods and as turtle methods declared deprecated (see docs of Python
> It didn't form 2.5 to 2.6 (at least not intentionally). But with the
> indroduction of the TurtleScreen class and the Screen class/object
> (singleton) a few of the turtle methods were also implemented as screen
> methods and as turtle methods declared deprecated (see docs of Python
> 2.6). These
On Aug 5, 12:19 am, Steven D'Aprano wrote:
> On Wed, 5 Aug 2009 03:49 pm Mensanator wrote:
>
> > In 3.1, tracing is now a screen attribute, not a turtle atribute.
> > I have no idea why
>
> > tooter = turtle.Turtle()
> > tooter.tracer(False)
>
> > doesn't give me an error (I thought silent err
Steven D'Aprano schrieb:
On Wed, 5 Aug 2009 03:49 pm Mensanator wrote:
In 3.1, tracing is now a screen attribute, not a turtle atribute.
I have no idea why
tooter = turtle.Turtle()
tooter.tracer(False)
doesn't give me an error (I thought silent errors were a bad thing).
What makes it an
Mensanator schrieb:
I hadn't noticed this before, but the overhaul of Turtle Graphics
dating
back to 2.6 has been broken as far as gmpy is concerned.
I hadn't noticed because I usually have tracing turned off (tracing
off
takes 3-4 seconds, tracing on takes 6-7 minutes).
In 3.1, tracing is now
On Wed, 5 Aug 2009 03:49 pm Mensanator wrote:
> In 3.1, tracing is now a screen attribute, not a turtle atribute.
> I have no idea why
>
> tooter = turtle.Turtle()
> tooter.tracer(False)
>
> doesn't give me an error (I thought silent errors were a bad thing).
What makes it an error? Do you
On Aug 4, 10:49 pm, Mensanator wrote:
> I hadn't noticed this before, but the overhaul of Turtle Graphics
> dating
> back to 2.6 has been broken as far as gmpy is concerned.
> The reason is that code in turtle.py was chabged from
>
> v2.5
> if self._drawing:
> if self._tracing:
I hadn't noticed this before, but the overhaul of Turtle Graphics
dating
back to 2.6 has been broken as far as gmpy is concerned.
I hadn't noticed because I usually have tracing turned off (tracing
off
takes 3-4 seconds, tracing on takes 6-7 minutes).
In 3.1, tracing is now a screen attribute, no
18 matches
Mail list logo
