This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients SnoopJeDi, barry, docs@python, eric.araujo, steven.daprano, terry.reedy
Date 2022-01-07.21:34:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
How about following "The Python interpreter has a number of functions and types built into it that are always available. They are listed here in alphabetical order." in
with "Here and elsewhere in these docs, entries for functions (including methods) that always return None usually omit 'Return None' and just say what the function does."

Barry: The PEP 8 'return None' recommendation could be added to the Reference entry for 'return'.  But I think this should be a separate issue as 1) it is about coding rather than documentation and 2) there is the possible objection that choosing completely explicit 'return None' versus half explicit, half implicit 'return' and the latter versus completely implicit <nothing at end> should be left to the style PEP.
Date User Action Args
2022-01-07 21:34:04terry.reedysetrecipients: + terry.reedy, barry, eric.araujo, steven.daprano, docs@python, SnoopJeDi
2022-01-07 21:34:03terry.reedysetmessageid: <>
2022-01-07 21:34:03terry.reedylinkissue46282 messages
2022-01-07 21:34:03terry.reedycreate