Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
gregorlingl mannequin opened this issue Sep 25, 2009 · 5 comments
Closed

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

gregorlingl mannequin opened this issue Sep 25, 2009 · 5 comments
Assignees
Labels
type-bug An unexpected behavior, bug, or error

Comments

@gregorlingl
Copy link
Mannequin

gregorlingl mannequin commented Sep 25, 2009

BPO 7001
Nosy @loewis, @birkenfeld, @bitdancer
Files
  • turtle_262_263.diff: bugfixes for three bugs
  • turtleDemo_262_263.diff: Adding one line, needed as a complement to the bugfixes in turtle_262_263.difff
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = 'https://github.com/bitdancer'
    closed_at = <Date 2009-09-28.18:58:05.533>
    created_at = <Date 2009-09-25.21:02:45.253>
    labels = ['type-bug']
    title = 'turtle.py bug-fixes, backported from 3.1 [issue5923]'
    updated_at = <Date 2009-09-28.18:58:05.531>
    user = 'https://bugs.python.org/gregorlingl'

    bugs.python.org fields:

    activity = <Date 2009-09-28.18:58:05.531>
    actor = 'r.david.murray'
    assignee = 'r.david.murray'
    closed = True
    closed_date = <Date 2009-09-28.18:58:05.533>
    closer = 'r.david.murray'
    components = []
    creation = <Date 2009-09-25.21:02:45.253>
    creator = 'gregorlingl'
    dependencies = []
    files = ['14976', '14977']
    hgrepos = []
    issue_num = 7001
    keywords = ['patch']
    message_count = 5.0
    messages = ['93142', '93143', '93154', '93163', '93225']
    nosy_count = 4.0
    nosy_names = ['loewis', 'georg.brandl', 'gregorlingl', 'r.david.murray']
    pr_nums = []
    priority = 'normal'
    resolution = 'fixed'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue7001'
    versions = ['Python 2.6', 'Python 2.7']

    @gregorlingl
    Copy link
    Mannequin Author

    gregorlingl mannequin commented Sep 25, 2009

    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,
    (1) in TurtleScreen.update()
    (2) in TurtleScreen.onkey()
    (3) in _Screen.__init__ and _Screen.setup

    The last one entails the need of adding one line into turtleDemo.py.
    This change does not affect the correct working of turtleDemo with the
    Python 2.6.2 turtle and demos.

    @gregorlingl
    Copy link
    Mannequin Author

    gregorlingl mannequin commented Sep 25, 2009

    !! This patch should be applied if and only if the corresponding one of
    turtle.py is applied !!

    @bitdancer
    Copy link
    Member

    Gregor, just to make sure I understand, these patches need to be applied
    to trunk (2.7) as well as 2.6, correct?

    @bitdancer bitdancer self-assigned this Sep 26, 2009
    @bitdancer bitdancer added the type-bug An unexpected behavior, bug, or error label Sep 26, 2009
    @gregorlingl
    Copy link
    Mannequin Author

    gregorlingl mannequin commented Sep 26, 2009

    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 to
    2.7. But there are quite a few amendments more that should be backported
    from Python 3.1 to Python 2.7. Moreover, we do not know today, which
    bugfixes etc. will go into 3.2 and I think 3.2 should be synchronized
    with 2.7. Since 2.7 still seems to be pretty far away, we can defer this
    for now and do it later together with the complementing pathes. As
    already said, it needs to be done eventually, anyhow.

    Regards,
    Gregor

    @bitdancer
    Copy link
    Member

    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.

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    type-bug An unexpected behavior, bug, or error
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant