Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOI0q-00DUBZ-0V for pgsql-announce@arkaria.postgresql.org; Mon, 01 Jul 2024 14:28:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sOI0o-002EXH-Ak for pgsql-announce@arkaria.postgresql.org; Mon, 01 Jul 2024 14:28:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOI0n-002EX8-Bh for pgsql-announce@lists.postgresql.org; Mon, 01 Jul 2024 14:28:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOI0k-004Uzc-2i for pgsql-announce@lists.postgresql.org; Mon, 01 Jul 2024 14:28:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=0+xnE2eBbX+V3zGEK/t9YN4zEscyGgAErD0AOrF9K9E=; b=CAebn0M8XrA/VGyxzKobaSNS0z cCWc0ilHz42CSYFeGqNCD2eWV2vyMa9gs1SxhXWELQcOiIAnUulSZkHWRPfADDhVnnnQ9X0oWBAyt vFwT1PkGBXZbIPLcPLDHeTuEZTP2rAy8loYyqrWHw78MES3mU0h1fxVksQWNTSIC1tdJulgHgEpO1 Ki6JzgQAeDLedy9/6eF0vuUjrUOwiiTCMCVBuT/LOnD/USdt6kxWNaYSLAbUvB07MEwuND2cqcurk nE/D67mMnMRcSE5fYAug5up6mgRuJ50YTZEXtYXyNo6PX7jN+dzMfOONTlDssxCS+cG6mZxWvjUIi lqzuiMcQ==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOI0i-00Cm2m-93 for pgsql-announce@lists.postgresql.org; Mon, 01 Jul 2024 14:28:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sOI0g-007au4-PT for pgsql-announce@lists.postgresql.org; Mon, 01 Jul 2024 14:28:02 +0000 Content-Type: multipart/mixed; boundary="===============0118476905537904135==" MIME-Version: 1.0 Subject: Psycopg 3.2 released To: PostgreSQL Announce From: Psycopg Development Team via PostgreSQL Announce Reply-To: daniele.varrazzo@gmail.com Date: Mon, 01 Jul 2024 14:28:01 +0000 Message-ID: <171984408163.699.14556402475906295559@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 8b8de3429146d71e50bec9aafdb9f4a41dbeee2505e85d3b04832eb3893a23e7 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============0118476905537904135== Content-Type: multipart/alternative; boundary="===============1058392748486198337==" MIME-Version: 1.0 --===============1058392748486198337== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable After 846 commits and close to two years in the making, we are very happy t= o announce the release of [Psycopg 3.2](https://www.psycopg.org/psycopg3/do= cs/)! This release adds several new features to the Psycopg 3 line, some of which= are: - support for Numpy scalar types - easier to use notifications reception - the possibility to run queries with PostgreSQL-format parameters - a row factory to return a scalar from a query - asynchronous, encrypted cancellations - support for the many new features added in the upcoming PostgreSQL v17 - OpenSSL 3.x bundled with binary packages A few bug bug fixes are included too, which have also been independently re= leased in the 3.1.20 package. Given the high level of compatibility between= 3.1 and 3.2, this could be the last release of the 3.1 line. For further details please check out: - [release notes](https://www.psycopg.org/psycopg3/docs/news.html#psycopg-3= -2) - [news entry](https://www.psycopg.org/articles/2024/06/30/psycopg-32-relea= sed/) Please note that several new features in the 3.2 release require libpq v17,= but, because PostgreSQL version 17 has not been released yet, they are not= immediately available in the binary packages. In order to use these featur= es you will need a development version of libpq 17 on your system and to us= e the Python or C source distribution. New packages bundling libpq v17 will= be released as soon as the official PostgreSQL 17 has been released. Thank you very much to everyone who contributed to the project, especially = to Denis Laxalde from [Dalibo](https://www.dalibo.com/), indefatigable libp= q explorer and always available to solve challenging problems! --- Psycopg, first v2, now v3, is the de-facto standard for the communication b= etween Python and PostgreSQL, two major components of innumerable businesse= s and mission-critical infrastructures. Maintaining such a critical library= to the highest standard of reliability, completeness, performance requires= a lot of care and work. If you are a Python and PostgreSQL user and would like to make sure that th= e interface between the two is well maintained and continuously improved, p= lease consider [supporting the project](https://github.com/sponsors/dvarraz= zo) and to be [one of our sponsors](https://www.psycopg.org/sponsors/) =F0= =9F=92=9C Happy hacking! -- Daniele --===============1058392748486198337== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Psycopg 3.2 released
 

Psycopg 3.2 released

After 846 commits and close to two years in= the making, we are very happy to announce the release of Psycopg 3.2!

This release adds several new features to t= he Psycopg 3 line, some of which are:

  • support for Num= py scalar types
  • easier to use n= otifications reception
  • the possibility= to run queries with PostgreSQL-format parameters
  • a row factory t= o return a scalar from a query
  • asynchronous, e= ncrypted cancellations
  • support for the= many new features added in the upcoming PostgreSQL v17
  • OpenSSL 3.x bun= dled with binary packages

A few bug bug fixes are included too, which= have also been independently released in the 3.1.20 package. Given the hig= h level of compatibility between 3.1 and 3.2, this could be the last releas= e of the 3.1 line.

For further details please check out:

Please note that several new features in th= e 3.2 release require libpq v17, but, because PostgreSQL version 17 has not= been released yet, they are not immediately available in the binary packag= es. In order to use these features you will need a development version of l= ibpq 17 on your system and to use the Python or C source distribution. New = packages bundling libpq v17 will be released as soon as the official Postgr= eSQL 17 has been released.

Thank you very much to everyone who contrib= uted to the project, especially to Denis Laxalde from Dalibo<= /a>, indefatigable libpq explorer and always available to solve challenging= problems!

Psycopg, first v2, now v3, is the de-facto = standard for the communication between Python and PostgreSQL, two major com= ponents of innumerable businesses and mission-critical infrastructures. Mai= ntaining such a critical library to the highest standard of reliability, co= mpleteness, performance requires a lot of care and work.

If you are a Python and PostgreSQL user and= would like to make sure that the interface between the two is well maintai= ned and continuously improved, please consider = supporting the project and to be one of our spo= nsors =F0=9F=92=9C

Happy hacking!

-- Daniele
This email was sent to you from Psycopg Development Team. It was delivered = on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Psycopg Development Team.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============1058392748486198337==-- --===============0118476905537904135==--