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 1sODTg-00D45K-AX for psycopg@arkaria.postgresql.org; Mon, 01 Jul 2024 09:37:40 +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 1sODTe-0000gz-BW for psycopg@arkaria.postgresql.org; Mon, 01 Jul 2024 09:37:38 +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 1sODTe-0000gr-4q for psycopg@lists.postgresql.org; Mon, 01 Jul 2024 09:37:38 +0000 Received: from mail-yb1-xb35.google.com ([2607:f8b0:4864:20::b35]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sODTb-004SgM-UI for psycopg@postgresql.org; Mon, 01 Jul 2024 09:37:37 +0000 Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-dfab4779d95so2670828276.0 for ; Mon, 01 Jul 2024 02:37:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719826653; x=1720431453; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=uofkL+46pm0UQ9N7ScSHzZVTIv27PXwlFFcFpyPujpk=; b=PNQF+n9hp6pEIOxiMua/Lh4vZBxlWctLLv/gmUK8q3lZSkA4vFuJrWD29UKf/ZQ/5n +w/rhANa7fzn5O39gX3WXwrXT7Q7UIT00RzsmgElsLK5PpZpqrlXtsGQYtrzaRf723Ch f1uJLGyd1SSfRiC4Tft3AxOglEyn0oxxzAZVjXwIa8GppoCvyKFb8nAEFsM++zDmrAIa Gdp2/Yl5s/Ud276NtYmKY5nz5CicbgntMO1ZWJl/CGw4ji1halgE/beiYOWZutSN1dEt NoiKNCVSl9zZNHmt93tKR5Qjqdc3QKmgJrITkh9LIphNT9QF/tNDe5Xb8ZZ/xlzkmuGa 20nQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719826653; x=1720431453; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=uofkL+46pm0UQ9N7ScSHzZVTIv27PXwlFFcFpyPujpk=; b=GnfJkO1GpFgT5YyGnceiNrGFmaWpJgDAkvJUx0gAD1UjDphIBHedjQoHBdxK+LcOWj 1xxpP0KAghETLO+gM5Xnuce+MgGavRYuCgoTzZltUxgJU9XlbneHleBToQzq2zX9SMA+ Sp7fR75HFQ8DmwguMApXN/QM0/im0EHO2yUNDOU0Tmc5jWUVM62qhyKklWbdqSalvBRi qYVEujAtFCPcortdNz7aGXYOe5LnN4ZzFdN1joRUJsoYUaJjErP6L42upcAh9zegRcDQ dciMhng+wMVtNjDU8qNrpLPPw+CXj0HBVzKlHX7Mwl39GJQ3VnzZlnVhrTlUu4sEV40A xcQg== X-Gm-Message-State: AOJu0YwAhrznB08z86TTZdqoBBW60MUA9AYX73oK/IREslknr5gw+TOC H1tKPKA6Vn7MZCODVbss5aud9UrHqixmxtzI7JCpMeHKai8tSZp+l6SsDATnBsbbYIUm9jn81H4 6NYKjQAyob6+O2KpHawqBwO8JAh0LceuY X-Google-Smtp-Source: AGHT+IGvR225XM5IZH3P7ogDsLQ4a/vnLquM+NSnWR0GWm/Nfz1IfYiFkPN/8jTfmpdJx4kW05sLeZH9UW4nEYOVLN0= X-Received: by 2002:a25:860e:0:b0:dfa:72cc:f88b with SMTP id 3f1490d57ef6-e036ec507ffmr5413893276.52.1719826653558; Mon, 01 Jul 2024 02:37:33 -0700 (PDT) MIME-Version: 1.0 From: Daniele Varrazzo Date: Mon, 1 Jul 2024 11:37:21 +0200 Message-ID: Subject: Psycopg 3.2 released To: Psycopg Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 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 to the upcoming PostgreSQL v17 - OpenSSL 3.x bundled 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 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 - news entry: https://www.psycopg.org/articles/2024/06/30/psycopg-32-released/ 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 features you will need a development version of libpq 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 PostgreSQL 17 has been released. Thank you very much to everyone who contributed to the project, especially to Denis Laxalde, indefatigable libpq explorer and always available to solve challenging problems! Really thank you! Happy hacking! -- Daniele