bpo-44135: issubclass documentation doesn't explain tuple semantic#26193
bpo-44135: issubclass documentation doesn't explain tuple semantic#26193ambv merged 1 commit intopython:mainfrom
Conversation
Fidget-Spinner
left a comment
There was a problem hiding this comment.
This LGTM! Thanks for submitting this PR.
|
BTW, I think it would be better if your issue title summarised what the change is about. So maybe |
Thanks for the suggestion. I'll try to do a better job of naming PRs in the future. :) |
|
This PR is stale because it has been open for 30 days with no activity. |
|
Sorry for the long wait Zack. @ambv sorry can I trouble you to take a look at this please? I'd appreciate a second pair of eyes. |
|
Thanks @zkneupper for the PR, and @ambv for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
…ehaves (pythonGH-26193) Co-authored-by: Zachary Kneupper <zachary.kneupper@gmail.com> (cherry picked from commit 08767c7) Co-authored-by: Zack Kneupper <zachary.kneupper@gmail.com>
|
GH-28091 is a backport of this pull request to the 3.10 branch. |
…ehaves (pythonGH-26193) This is a quasi-backport to 3.9 since the wording in this branch is different. Co-authored-by: Zachary Kneupper zachary.kneupper@gmail.com
bpo-44135: issubclass documentation doesn't explain tuple semantic
https://bugs.python.org/issue44135
https://bugs.python.org/issue44135