From 06f77300aaf3c374b506094769cdf29372ffabcd Mon Sep 17 00:00:00 2001
From: Barry Warsaw <barry@python.org>
Date: Tue, 5 Sep 2017 18:01:21 -0700
Subject: [PATCH] Don't use `return Py_None` as the example.

We now have the `Py_RETURN_NONE` macro, which is better style, so don't use an
example that may conflict with that style.  Use a generic example.
---
 pep-0007.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pep-0007.txt b/pep-0007.txt
index bceac1bef..d9459acb7 100644
--- a/pep-0007.txt
+++ b/pep-0007.txt
@@ -1,4 +1,4 @@
-PEP: 7
+aPEP: 7
 Title: Style Guide for C Code
 Version: $Revision$
 Last-Modified: $Date$
@@ -104,8 +104,8 @@ Code lay-out
 
 * The return statement should *not* get redundant parentheses::
 
-      return Py_None; /* correct */
-      return(Py_None); /* incorrect */
+      return albatross; /* correct */
+      return(albatross); /* incorrect */
 
 * Function and macro call style: ``foo(a, b, c)`` -- no space before
   the open paren, no spaces inside the parens, no spaces before