| commit | 2ff7c913d92d8540e8b00c54746ce2f565521256 | |
| author | Michael Paquier <michael@paquier.xyz> | |
| Mon, 25 Nov 2024 00:15:25 +0000 (25 09:15 +0900) | ||
| committer | Michael Paquier <michael@paquier.xyz> | |
| Mon, 25 Nov 2024 00:15:25 +0000 (25 09:15 +0900) | ||
| tree | 1bf62612f63a6f447b1bcca374d4083f27101c41 | treesnapshot (tar.gz zip) |
| parent | 5de08f136ad690cde9a99c09c398ddb0c9272f11 | commitdiff |
doc: Fix example with __next__() in PL/Python function
Per PEP 3114, iterator.next() has been renamed to iterator.__next__(),
and one example in the documentation still used next(). This caused the
example provided to fail the function creation since Python 2 is not
supported anymore since 19252e8ec93.
Author: Erik Wienhold
Discussion: https://postgr.es/m/173209043143.2092749.13692266486972491694@wrigleys.postgresql.org
Backpatch-through: 15
Per PEP 3114, iterator.next() has been renamed to iterator.__next__(),
and one example in the documentation still used next(). This caused the
example provided to fail the function creation since Python 2 is not
supported anymore since 19252e8ec93.
Author: Erik Wienhold
Discussion: https://postgr.es/m/173209043143.2092749.13692266486972491694@wrigleys.postgresql.org
Backpatch-through: 15
| doc/src/sgml/plpython.sgml | diffblobblamehistory |