Brett Cannon <br...@python.org> added the comment:

If you can't find the guidance then please either open an issue or submit a PR 
to update the devguide with the info.

As for why your other PR was accepted, that was fixing an actual bug in the 
docstring. This one has absolutely no semantic change to Python; it's the 
equivalent of changing some whitespace just because it isn't quite in line with 
PEP 8. It simply isn't worth the overhead of the PR review or the churn on the 
file as now the `git blame` info is off for who last made a semantic change to 
that line.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue40753>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to