Some comments on PL/Python documentation

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: gri(dot)bogdan(dot)2020(at)gmail(dot)com
Subject: Some comments on PL/Python documentation
Date: 2024-12-29 00:48:25
Message-ID: 173543330569.680.6706329879058172623@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/17/plpython-data.html
Description:

Hello,
In my opinion, some phrases on this page are not quite correct.

44.2.4. Composite Types
You say: '...Object (any object providing method __getattr__)...'
Actually, the object class provides the __getattribute__() method but not
the __getattr__() method.
See https://docs.python.org/3/reference/datamodel.html#object.__getattr__

44.2.5. Set-Returning Functions
1. You say: '...Sequence type (tuple, list, set)...'
Being an unordered collection, sets do not record element position or order
of insertion. Accordingly, sets do not support indexing, slicing, or other
sequence-like behavior.
See
https://docs.python.org/3/library/stdtypes.html#set-types-set-frozenset

2. You say: '...Iterator (any object providing __iter__ and next
methods)...'
Actually, the iterator objects must support the __next__() method.
See https://docs.python.org/3/glossary.html#term-iterator

Regards,
Bogdan Grigorenko

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2024-12-30 12:06:40 LC_COLLATE is visible in the documentation for PostgreSQL 17, but it is not supported
Previous Message Bruce Momjian 2024-12-28 19:31:03 Re: which wire protocol fields are signed int and which ones are unsigned