-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
Move __missing__ after __delitem__ in Data model #10923
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
Move __missing__ after __delitem__ in Data model #10923
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would move also .. index:: object: slice
before .. note::
.
@serhiy-storchaka I agree with your suggestion. |
Thanks @andresdelfino for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.6, 3.7. |
(cherry picked from commit 1ce853f) Co-authored-by: Andre Delfino <adelfino@gmail.com>
GH-10938 is a backport of this pull request to the 3.7 branch. |
(cherry picked from commit 1ce853f) Co-authored-by: Andre Delfino <adelfino@gmail.com>
GH-10939 is a backport of this pull request to the 3.6 branch. |
Sorry, @andresdelfino and @serhiy-storchaka, I could not cleanly backport this to |
(cherry picked from commit 1ce853f) Co-authored-by: Andre Delfino <adelfino@gmail.com>
(cherry picked from commit 1ce853f) Co-authored-by: Andre Delfino <adelfino@gmail.com>
GH-10944 is a backport of this pull request to the 2.7 branch. |
Doc says "Slicing is done exclusively with the following three methods", and it was correct until b67f6e2 . Since then, it documents __missing__ between __getitem__ and __setitem__.