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:
parent
8033f84558
commit
06f77300aa
|
@ -1,4 +1,4 @@
|
||||||
PEP: 7
|
aPEP: 7
|
||||||
Title: Style Guide for C Code
|
Title: Style Guide for C Code
|
||||||
Version: $Revision$
|
Version: $Revision$
|
||||||
Last-Modified: $Date$
|
Last-Modified: $Date$
|
||||||
|
@ -104,8 +104,8 @@ Code lay-out
|
||||||
|
|
||||||
* The return statement should *not* get redundant parentheses::
|
* The return statement should *not* get redundant parentheses::
|
||||||
|
|
||||||
return Py_None; /* correct */
|
return albatross; /* correct */
|
||||||
return(Py_None); /* incorrect */
|
return(albatross); /* incorrect */
|
||||||
|
|
||||||
* Function and macro call style: ``foo(a, b, c)`` -- no space before
|
* Function and macro call style: ``foo(a, b, c)`` -- no space before
|
||||||
the open paren, no spaces inside the parens, no spaces before
|
the open paren, no spaces inside the parens, no spaces before
|
||||||
|
|
Loading…
Reference in New Issue