docs: document that ticket #254 is fixed in 3.0.12

We can consider this just a bug, not a change of interface. It is
particularly bad because it doesn't allow to pipe a COPY FROM into a
COPY TO.

See https://github.com/psycopg/psycopg/discussions/285#discussioncomment-2663192
for details.

diff --git a/docs/api/objects.rst b/docs/api/objects.rst
index b4e277eeb77ee3272b51b3965e8f2bd0ed144517..419606c24e690d2898db5fae2a16e6afe5d289ff 100644 (file)
--- a/docs/api/objects.rst
+++ b/docs/api/objects.rst
@@ -137,11 +137,6 @@ COPY-related objects
         see :ref:`adaptation` for details.
 
     .. automethod:: write
-
-        .. versionchanged:: 3.1
-
-            accept `bytearray` and `memoryview` data as input too.
-
     .. automethod:: read
 
         Instead of using `!read()` you can iterate on the `!Copy` object to

diff --git a/docs/news.rst b/docs/news.rst
index 7a4728bf31b2cb2a5b62a4809948528b9f37975e..1a54b8789658013ca4a2da3a4f10a0920100a386 100644 (file)
--- a/docs/news.rst
+++ b/docs/news.rst
@@ -22,14 +22,14 @@ Psycopg 3.1 (unreleased)
 - Add `pq.PGconn.trace()` and related trace functions (:ticket:`#167`).
 - Add ``prepare_threshold`` parameter to `Connection` init (:ticket:`#200`).
 - Add `Error.pgconn` and `Error.pgresult` attributes (:ticket:`#242`).
-- Allow `bytearray`/`memoryview` data too as `Copy.write()` input
-  (:ticket:`#254`).
 - Drop support for Python 3.6.
 
 
 Psycopg 3.0.12 (unreleased)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
+- Allow `bytearray`/`memoryview` data too as `Copy.write()` input
+  (:ticket:`#254`).
 - Fix dumping `~enum.IntEnum` in text mode, Python implementation.