Serhiy Storchaka added the comment: Here is a filtered results of find * -name '*.rst' -exec egrep -n -w -B1 -A1 'I|me|my' '{}' + ---------- Added file: http://bugs.python.org/file30665/Imemy.grep _______________________________________ Python tracker http://bugs.python.org/issue18280 _______________________________________

Terry J. Reedy added the comment: I find some anonymous I references (Guido? 20 years ago?) off-putting when reading the doc as formal reference. ---------- nosy: +terry.reedy _______________________________________ Python tracker http://bugs.python.org/issue18280 _______________________________________

Changes by A.M. Kuchling : ---------- nosy: -akuchling _______________________________________ Python tracker http://bugs.python.org/issue18280 _______________________________________

Raymond Hettinger added the comment: Fred, do you want to opine on this? In some cases, like heapq.py, the personal touch is an essential and beautiful part of the presentation and is a cherished part of Python. In other cases, it seems unnecessary or a little off-putting, so perhaps a few changes are warranted. Personally, I've grown to really dislike the incessant stream of proposals to make broad sweeping trivial changes across the code or documentation to fix made-up problems (ones not reported or cared about by actual users). In particular, I worry about sending some new dev on a mission to rewrite documentation that was written by domain experts (Alex Martelli reported that copy-editors "wreaked havoc" on one of his books just prior to publication by subtly changing the meaning or correctness of his prose while applying grammar rules and minor style edits -- I wish to avoid the same for us). Also, I place high value on text written by Guido and think we lose something every time someone wants to rewrite it to fit their personal tastes and views of the language. The tastes and views of module authors are more important are easily lost in style edits (especially those that change point of view, mood, or theme of presentation). Another thought is that there should be different general rules for different sections. The standard library docs tend to be more formal. The language reference tends to be even more formal ("for language lawyers"). The tutorial tends to be personable. The how-to guides are often have a personal touch and are the only places where we attribute authorship back individuals (actual by-lines at the top of the file). [Cheryl Sabella]

Would it be OK for me to tackle this? You could, but I would really like to get you involved in more substantive work that involves thinking about real issues and real code. IMO, this project isn't worthy of you time and is not on the critical path to your stated goals. That said, feel free to volunteer for anything that interests you.

---------- assignee: docs@python -> fdrake nosy: +fdrake, rhettinger versions: +Python 3.7 -Python 2.7, Python 3.3, Python 3.4 _______________________________________ Python tracker http://bugs.python.org/issue18280 _______________________________________

Guido van Rossum added the comment: Marking this as "easy". People are welcome to submit PRs that fix the wording in one or a small number of modules called out in Serhiy's list. ---------- keywords: +easy nosy: +gvanrossum _______________________________________ Python tracker https://bugs.python.org/issue18280 _______________________________________

Serhiy Storchaka added the comment: I think they are not required, but recommended.

From https://www.python.org/dev/peps/pep-0008/#comments:

You should use two spaces after a sentence-ending period in multi- sentence comments, except after the final sentence.

From https://www.python.org/dev/peps/pep-0012/#general:

You must adhere to the Emacs convention of adding two spaces at the end of every sentence. AFAIK in English typography the space after a sentence-ending period is longer than spaces between words. In other European typographies they have the same width. ---------- _______________________________________ Python tracker https://bugs.python.org/issue18280 _______________________________________

Change by Raymond Hettinger : ---------- nosy: -rhettinger _______________________________________ Python tracker https://bugs.python.org/issue18280 _______________________________________

Change by Michael Felt : ---------- keywords: +patch pull_requests: +20780 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21639 _______________________________________ Python tracker https://bugs.python.org/issue18280 _______________________________________

Change by Georg Brandl : ---------- nosy: -georg.brandl _______________________________________ Python tracker https://bugs.python.org/issue18280 _______________________________________