8000 Add 'The Python 2.3 Method Resolution Order' by hugovk · Pull Request #116435 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

Add 'The Python 2.3 Method Resolution Order' #116435

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.

Sign up for GitHub

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

Merged
merged 7 commits into from
Apr 15, 2024
Merged

Add 'The Python 2.3 Method Resolution Order' #116435

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
91e7802
Add 'The Python 2.3 Method Resolution Order'
hugovk Mar 6, 2024
aaae147
Update formatting and links
hugovk Mar 6, 2024
4226a20
Update links to new docs page
hugovk Mar 6, 2024
029b946
Fix doctests
hugovk Mar 11, 2024
3627b00
Goodybye ö/\/\/\/\/ ä--__--___
hugovk Mar 11, 2024
d960514
Note this is a historical document
hugovk Mar 12, 2024
76f79b1
Remove jgs acknowledgment from this copy, after removing the ASCII sn…
hugovk Mar 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix doctests
  • Loading branch information
@hugovk
hugovk committed Mar 11, 2024
commit 029b946b64f34be326643175511a7dff5f4b0859
16 changes: 8 additions & 8 deletions Doc/howto/mro.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -382,10 +382,10 @@ A lazy programmer can obtain the MRO directly from Python 2.2, since in
this case it coincides with the Python 2.3 linearization. It is enough
to invoke the .mro() method of class A:

>>> A.mro()
(<class '__main__.A'>, <class '__main__.B'>, <class '__main__.E'>,
<class '__main__.C'>, <class '__main__.D'>, <class '__main__.F'>,
<type 'object'>)
>>> A.mro() # doctest: +NORMALIZE_WHITESPACE
[<class 'A'>, <class 'B'>, <class 'E'>,
<class 'C'>, <class 'D'>, <class 'F'>,
<class 'object'>]

Finally, let me consider the example discussed in the first section,
involving a serious order disagreement. In this case, it is
Expand Down Expand Up @@ -434,7 +434,7 @@ following example:

>>> F=type('Food',(),{'remember2buy':'spam'})
>>> E=type('Eggs',(F,),{'remember2buy':'eggs'})
>>> G=type('GoodFood',(F,E),{}) # under Python 2.3 this is an error!
>>> G=type('GoodFood',(F,E),{}) # under Python 2.3 this is an error! # doctest: +SKIP

with inheritance diagram

Expand All @@ -456,7 +456,7 @@ we would expect the attribute *G.remember2buy* to be inherited by
*F.rembermer2buy* and not by *E.remember2buy*: nevertheless Python 2.2
gives

>>> G.remember2buy
>>> G.remember2buy # doctest: +SKIP
'eggs'

This is a breaking of local precedence ordering since the order in the
Expand All @@ -473,8 +473,8 @@ it is a different from old style classes:

>>> class F: remember2buy='spam'
>>> class E(F): remember2buy='eggs'
>>> class G(F,E): pass
>>> G.remember2buy
>>> class G(F,E): pass # doctest: +SKIP
>>> G.remember2buy # doctest: +SKIP
'spam'

In this case the MRO is GFEF and the local precedence ordering is
Expand Down
0