[issue7001] turtle.py bug-fixes, backported from 3.1 [issue5923]

R. David Murray added the comment: Committed to trunk in r75115, and 2.6 in r75116. As far as I know there are no tests for this module other than the doctests in the documentation. Those at least run without errors after the patches. -- resolution: -> fixed stage: commit review -> c

[issue7001] turtle.py bug-fixes, backported from 3.1 [issue5923]

Gregor Lingl added the comment: These patches need to be applied to 2.6 in order that they appear in 2.6.3. (/python/branches/release26-maint, I think). As far as I see this is urgent because 2.6.3rc1 is only a few days away. Eventually (or, if you want at the same time) they need to be applied

[issue7001] turtle.py bug-fixes, backported from 3.1 [issue5923]

R. David Murray added the comment: Gregor, just to make sure I understand, these patches need to be applied to trunk (2.7) as well as 2.6, correct? -- assignee: -> r.david.murray nosy: +r.david.murray priority: -> normal stage: -> commit review type: -> behavior versions: +Python 2.

[issue7001] turtle.py bug-fixes, backported from 3.1 [issue5923]

Gregor Lingl added the comment: !! This patch should be applied if and only if the corresponding one of turtle.py is applied !! -- nosy: +georg.brandl, loewis Added file: http://bugs.python.org/file14977/turtleDemo_262_263.diff ___ Python tracker

[issue7001] turtle.py bug-fixes, backported from 3.1 [issue5923]

New submission from Gregor Lingl : Among the changes of turtle.py from Python 3.0 to Python 3.1 there were three bugfixes. Those bugs appear also in the Python 2.6 version of turtle.py imho these should be fixed for Python 2.6.3 The appended diffs contain the (backported) fixes of these bugs, (