From: Daniele Varrazzo Date: Sat, 29 Nov 2025 18:45:50 +0000 (+0100) Subject: docs: 3.3 release notes cleanup and other small fixes X-Git-Tag: 3.3.0~4 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=90f8606eefd3cd1de76934ca307899c9ff5cf55b;p=thirdparty%2Fpsycopg.git docs: 3.3 release notes cleanup and other small fixes --- diff --git a/docs/basic/transactions.rst b/docs/basic/transactions.rst index 20dc76f3f..f69b68acf 100644 --- a/docs/basic/transactions.rst +++ b/docs/basic/transactions.rst @@ -309,8 +309,8 @@ Each `!Transaction` object exposes a `~Transaction.status` property allowing to inspect the current state of the transaction. This can be useful for debugging, logging, or implementing custom transaction management logic. -The `!status` property is a `~psycopg.Transaction.Status` enum value: -please check the enum documentation for the possible values. +The `!status` property is a `psycopg.Transaction.Status` enum value: +please check its documentation for the possible values. Here are a few examples of how to use the `!status` property: @@ -346,7 +346,7 @@ Here are a few examples of how to use the `!status` property: The `!status` property remains accessible after the transaction context has exited, allowing you to check the final outcome of the transaction even after -the `!with` block completes. This is particularly useful when you need to log +the `!with` block has exited. This is particularly useful when you need to log transaction outcomes or implement retry logic based on the transaction status. diff --git a/docs/basic/tstrings.rst b/docs/basic/tstrings.rst index 15d5413e8..ccd7f37eb 100644 --- a/docs/basic/tstrings.rst +++ b/docs/basic/tstrings.rst @@ -144,7 +144,7 @@ result in executing the statement ``NOTIFY "foo.bar", 'O''Reilly'``. Example: nested templates ------------------------- -A string template merges literal parts of the query with parameter. It is also +A string template merges literal parts of the query with parameters. It is also possible to pass templates to templates in order to compose more and more complex and dynamic SQL statements. diff --git a/docs/news.rst b/docs/news.rst index 8136ca051..8ac93a2cd 100644 --- a/docs/news.rst +++ b/docs/news.rst @@ -19,8 +19,9 @@ Psycopg 3.3.0 (unreleased) - More flexible :ref:`composite adaptation`: it is now possible to adapt Python objects to PostgreSQL composites and back even if they are not sequences or if they take keyword arguments (:ticket:`#932`, :ticket:`#1202`). -- Cursors are now *iterators*, not only *iterables*. This means you can call - ``next(cur)`` to fetch the next row (:ticket:`#1064`). +- Cursors are now iterators_, not just iterables_. This means you can call + `next`\ ``(cur)`` or `anext`\ ``(cur)``, which is useful as a :ref:`type-safe + expression ` (:ticket:`#1064`). - Add `Cursor.set_result()` and `Cursor.results()` to move across the result sets of queries executed though `~Cursor.executemany()` or `~Cursor.execute()` with multiple statements (:tickets:`#1080, #1170`). @@ -50,6 +51,9 @@ Psycopg 3.3.0 (unreleased) - Drop support for Python 3.8 (:ticket:`#976`) and 3.9 (:ticket:`#1056`). +.. _iterators: https://docs.python.org/3/glossary.html#term-iterator +.. _iterables: https://docs.python.org/3/glossary.html#term-iterable + Current release ---------------