From 140e6ad4f2e458a74630849b1ccba1219c72164a Mon Sep 17 00:00:00 2001 From: Daniele Varrazzo Date: Fri, 26 Feb 2010 00:37:09 +0000 Subject: [PATCH] Added notes about stuff changed in ver. 2.0.14. --- doc/src/extensions.rst | 2 +- doc/src/usage.rst | 12 +++++------- 2 files changed, 6 insertions(+), 8 deletions(-) diff --git a/doc/src/extensions.rst b/doc/src/extensions.rst index 3f4959ea..e2e68664 100644 --- a/doc/src/extensions.rst +++ b/doc/src/extensions.rst @@ -182,7 +182,7 @@ deal with Python objects adaptation: >>> Binary("\x00\x08\x0F").getquoted() "'\\\\000\\\\010\\\\017'" - .. versionchanged:: 2.0.14(ish) + .. versionchanged:: 2.0.14 previously the adapter was not exposed by the `extensions` module. In older version it can be imported from the implementation module `!psycopg2._psycopg`. diff --git a/doc/src/usage.rst b/doc/src/usage.rst index c57b3da2..5662c7c4 100644 --- a/doc/src/usage.rst +++ b/doc/src/usage.rst @@ -286,15 +286,13 @@ the SQL string that would be sent to the database. SQL doesn't allow an empty list in the IN operator, so your code should guard against empty tuples. - .. note:: - - The IN adapter is automatically registered when the - `~psycopg2.extensions` module is imported. This behaviour may change - in the future and the adapter will probably be always active. - .. versionadded:: 2.0.6 - the tuple :sql:`IN` adaptation. + the tuple :sql:`IN` adaptation. + .. versionchanged:: 2.0.14 + the tuple :sql:`IN` adapter is always active. In previous releases it + was necessary to import the `~psycopg2.extensions` module to have it + registered. .. index:: single: Unicode