MIME-Version: 1.0
From: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: Thu, 11 Apr 2024 09:56:22 +0200
Message-ID: 
 <CA+mi_8YaYErxx0L56Z1HdXkMmdMd-TSYZ=UDjQZAOSQ4zUTKPQ@mail.gmail.com>
Subject: Waiting for Psycopg 3.2
To: Psycopg <psycopg@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000074a03d0615cd7e5c"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2Bmi_8YaYErxx0L56Z1HdXkMmdMd-TSYZ%3DUDjQZAOSQ4zUTKPQ%40mail.gmail.com>
Precedence: bulk

--00000000000074a03d0615cd7e5c
Content-Type: text/plain; charset="UTF-8"

Hello list!

There is currently a flurry of activities around the Psycopg 3 repository,
motivated especially by the PostgreSQL 17 feature freeze, whose libpq
exposes a set of features which turned out very useful.

Therefore, after a round of merging and some scheduled refactoring [1], we
should be able to merge a version 3.2. We have gathered a considerable list
of features [2] and we are looking forward to releasing them. Some of the
highlights are:

- support for numpy scalars,
- an easier to use notifications generator,
- support for asynchronous and safe cancel,
- prepared statements compatible with PgBouncer.

One notable absent from the list of features scheduled for release is the
numpy arrays adaptation. I have always thought that it would be natural to
have such feature... but fundamentally nobody ever voiced a need for it.
Therefore I prefer to postpone it to a later time [3] and not delay the
release further.

In order to reduce the maintenance chore, we have developed a system to
generate the synchronous code from the AST of the async code. If anyone has
a similar need, maintaining a codebase in both sync and async variants,
they are welcome to take a look [4] and lift whatever useful.

Feedback about the upcoming release is welcome! In the meantime I'd like to
thank our <https://www.psycopg.org/sponsors/> and everyone who has
contributed ideas, reports, code, in particular Denis "@dlax" Laxalde who
has brought plenty of ideas and good code.

I am looking forward to get back with news of a final 3.2 release in a few
weeks time. In the meantime, happy hacking!

-- Daniele

[1] https://github.com/psycopg/psycopg/milestone/5
[2] https://www.psycopg.org/psycopg3/docs/news.html#psycopg-3-2-unreleased
[3] https://github.com/psycopg/psycopg/issues/336
[4] https://github.com/psycopg/psycopg/blob/master/tools/async_to_sync.py

--00000000000074a03d0615cd7e5c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hello list!<div dir=3D"auto"><br></div><div dir=3D"auto">=
There is currently a flurry of activities around the Psycopg 3 repository, =
motivated especially by the PostgreSQL 17 feature freeze, whose libpq expos=
es a set of features which turned out very useful.</div><div dir=3D"auto"><=
br></div><div dir=3D"auto">Therefore, after a round of merging and some sch=
eduled refactoring [1], we should be able to merge a version 3.2. We have g=
athered a considerable list of features [2] and we are looking forward to r=
eleasing them. Some of the highlights are:=C2=A0</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">- support for numpy scalars,</div><div dir=3D"auto=
">- an easier to use notifications generator,</div><div dir=3D"auto">- supp=
ort for asynchronous and safe cancel,</div><div dir=3D"auto">- prepared sta=
tements compatible with PgBouncer.</div><div dir=3D"auto"><br></div><div di=
r=3D"auto">One notable absent from the list of features scheduled for relea=
se is the numpy arrays adaptation. I have always thought that it would be n=
atural to have such feature... but fundamentally nobody ever voiced a need =
for it. Therefore I prefer to postpone it to a later time [3] and not delay=
 the release further.</div><div dir=3D"auto"><br></div><div dir=3D"auto">In=
 order to reduce the maintenance chore, we have developed a system to gener=
ate the synchronous code from the AST of the async code. If anyone has a si=
milar need, maintaining a codebase in both sync and async variants, they ar=
e welcome to take a look [4] and lift whatever useful.</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">Feedback about the upcoming release is welco=
me! In the meantime I&#39;d like to thank our &lt;<a href=3D"https://www.ps=
ycopg.org/sponsors/">https://www.psycopg.org/sponsors/</a>&gt; and everyone=
 who has contributed ideas, reports, code, in particular Denis &quot;@dlax&=
quot; Laxalde who has brought plenty of ideas and good code.</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">I am looking forward to get back with=
 news of a final 3.2 release in a few weeks time. In the meantime, happy ha=
cking!</div><div dir=3D"auto"><br></div><div dir=3D"auto">-- Daniele</div><=
div dir=3D"auto"><br></div><div dir=3D"auto">[1] <a href=3D"https://github.=
com/psycopg/psycopg/milestone/5">https://github.com/psycopg/psycopg/milesto=
ne/5</a></div><div dir=3D"auto">[2] <a href=3D"https://www.psycopg.org/psyc=
opg3/docs/news.html#psycopg-3-2-unreleased">https://www.psycopg.org/psycopg=
3/docs/news.html#psycopg-3-2-unreleased</a></div><div dir=3D"auto">[3] <a h=
ref=3D"https://github.com/psycopg/psycopg/issues/336">https://github.com/ps=
ycopg/psycopg/issues/336</a></div><div dir=3D"auto">[4] <a href=3D"https://=
github.com/psycopg/psycopg/blob/master/tools/async_to_sync.py">https://gith=
ub.com/psycopg/psycopg/blob/master/tools/async_to_sync.py</a></div><div dir=
=3D"auto"><br></div></div>

--00000000000074a03d0615cd7e5c--