bpo-37730: Fix usage of NotImplemented instead of NotImplementedError in docs#15062
Conversation
|
Thanks @dhdavvie for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 2.7, 3.7, 3.8. |
|
GH-15063 is a backport of this pull request to the 3.8 branch. |
|
Sorry, @dhdavvie and @serhiy-storchaka, I could not cleanly backport this to |
… in docs. (pythonGH-15062) (cherry picked from commit ed5e8e0) Co-authored-by: David H <dheiberg@mozilla.com>
|
Sorry @dhdavvie and @serhiy-storchaka, I had trouble checking out the |
|
Does this branch need to be open for the cherry picking? |
|
GH-15106 is a backport of this pull request to the 3.7 branch. |
…dError in docs. (pythonGH-15062). (cherry picked from commit ed5e8e0) Co-authored-by: David H <dheiberg@mozilla.com>
|
@dhdavvie, do you mind to create a backport to 2.7? |
… in docs. (pythonGH-15062) (cherry picked from commit ed5e8e0)
…dError in docs. (pythonGH-15062). (cherry picked from commit ed5e8e0) Co-authored-by: David H <dheiberg@mozilla.com>
As mentioned in the BPO, there are some instances where NotImplemented is used when NotImplementedError was meant to be. This is the example I found after running
rg -e NotImplemented[^E] Doc/, all other usages looked correct.I have updated the
Doc/library/winreg.rstfile, and then noticed that the Clinic comments forPC/winreg.cwere also incorrect. I updated these and ranpython3 Tools/clinic/clinic.py PC/winreg.cto generate the new output. This is my first time fixing the docs here so if I have missed a stephttps://bugs.python.org/issue37730