Tutorial section 9.5.1 ignores MRO for new-style classes

[gazzadee]

BPO	1382213
Nosy	@rhettinger

^{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/rhettinger'
closed_at = <Date 2007-04-03.01:40:29.000>
created_at = <Date 2005-12-16.07:08:32.000>
labels = ['docs']
title = 'Tutorial section 9.5.1 ignores MRO for new-style classes'
updated_at = <Date 2007-04-03.01:40:29.000>
user = 'https://bugs.python.org/gazzadee'

bugs.python.org fields:

activity = <Date 2007-04-03.01:40:29.000>
actor = 'rhettinger'
assignee = 'rhettinger'
closed = True
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2005-12-16.07:08:32.000>
creator = 'gazzadee'
dependencies = []
files = []
hgrepos = []
issue_num = 1382213
keywords = []
message_count = 2.0
messages = ['27089', '27090']
nosy_count = 2.0
nosy_names = ['rhettinger', 'gazzadee']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1382213'
versions = ['Python 2.4']

[gazzadee]

Section 9.5.1 ("Multiple Inheritance") of the tutorial
(as viewed on http://www.python.org/doc/2.4.2/tut/)
discusses the Method Resolution Order (MRO) for classes
with multiple inheritance.

However, the 2nd paragraph incorrectly states that "The
only rule necessary to explain the semantics is the
resolution rule used for class attribute references.
This is depth-first, left-to-right". Whilst this is
true for old-style classes, new-style classes use a
different MRO (as documented elsewhere - eg.
http://www.python.org/2.3/mro.html)

[rhettinger]

Fixed. See versions 54667 and 54668.