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.
This commit is contained in:
Barry Warsaw 2017-09-05 18:01:21 -07:00
parent 8033f84558
commit 06f77300aa
1 changed files with 3 additions and 3 deletions

View File

@ -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