bpo-33885: Replace "hook function" with "callable"#7765
bpo-33885: Replace "hook function" with "callable"#7765terryjreedy merged 1 commit intopython:3.6from
Conversation
|
Thanks @andresdelfino for the PR, and @terryjreedy for merging it 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.6, 3.7. |
|
GH-7861 is a backport of this pull request to the 3.7 branch. |
(cherry picked from commit c45cb47) Co-authored-by: Andrés Delfino <adelfino@gmail.com>
|
Sorry, @andresdelfino and @terryjreedy, I could not cleanly backport this to |
|
Sorry, @andresdelfino and @terryjreedy, I could not cleanly backport this to |
|
Andres, the backports are yours if you think them worthwhile. Ditto for 'complete progams', if the issue comes up. |
Regarding the first item, the backport to 3.6 is no need, as the commit has merged into that branch already. I'll make the backport for 2.7. And a forwardport(?) for this to master. Or should we proceed otherwise? |
|
Regarding the third item, I see you were talking about #7744 :) |
|
There are 3 options. I am going to ask on core_mentorship which is preferred. |
|
OK, I'll wait. Sorry for the inconvenience... |
|
On core_mentorship, Nick Coughlin said "Just cherry pick to the full set of destinations from the original |
|
Great! I'll do it right away. Sorry for the hassle. |
…). (cherry picked from commit c45cb47) Co-authored-by: Andrés Delfino <adelfino@gmail.com>
|
GH-7885 is a backport of this pull request to the 2.7 branch. |
|
Repositories are intentionally mistake resilient. The guaranteed way to never make a bad merge is to never make a merge. There have been people who have done the latter after getting commit privileges. |
|
Oh, I already opened the PR, but it didn't reference this one. LEt me grab the link |
|
already committed, though :) |
|
I guess "needs backport to 3.6" tag should be removed. |
https://bugs.python.org/issue33885