pgsql: Use Py_RETURN_NONE where suitable

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use Py_RETURN_NONE where suitable
Date: 2017-09-29 20:52:35
Message-ID: E1dy2Gx-00031e-CU@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use Py_RETURN_NONE where suitable

This is more idiomatic style and available as of Python 2.4, which is
our minimum.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/0008a106d4f84206a96fc1fb09a1e6b09f1627ec

Modified Files
--------------
src/pl/plpython/plpy_cursorobject.c | 3 +--
src/pl/plpython/plpy_plpymodule.c | 3 +--
src/pl/plpython/plpy_subxactobject.c | 3 +--
3 files changed, 3 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2017-09-30 00:29:57 pgsql: Extend & revamp pg_bswap.h infrastructure.
Previous Message Tom Lane 2017-09-29 20:26:42 pgsql: Fix inadequate locking during get_rel_oids().