Back to Explore

psycopg/psycopg2

GitHub
1 updates · last 90 days1 watchersOpen source

Last release: 1 month ago

psycopg2 is a PostgreSQL database adapter for Python, providing a way for Python applications to connect to and work with PostgreSQL. It’s useful if you need Python-to-PostgreSQL connectivity and want to manage database interactions from your code.

Project status

  • Actively maintained: The source has recent activity (latest upstream push on 2026-05-02) and tagged 2.9.12 updates in 2026-04-20, indicating it is still under active development and release engineering.
  • Update cadence (apparent): Updates appear periodically, with the last two main version updates roughly 6 months apart (2.9.11 on 2025-10-09, 2.9.12 on 2026-04-20). Earlier history also suggests longer but recurring maintenance intervals (for example, about 1 year between 2.9.10 (2024-10-15) and 2.9.11 (2025-10-09).

AI summary generated 2 weeks ago

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • 2.9.12

    1 month ago

    psycopg 2.9.12 is a small release centered on a fix for the malformed interval parser infinite loop, plus a refresh of build and packaging workflows. The code also updates build-time dependencies and wheel-building infrastructure, with the most notable hidden impact being a tighter Linux aarch64 wheel baseline.

  • 2.9.11-riscv64

    7 months ago

    The release notes are effectively empty, only marking version 2.9.11-riscv64. The code diff shows this is a packaging and CI release that adds riscv64 Linux wheel support, introduces a dedicated libpq cache workflow, and broadens build-script support for Rocky Linux.

  • 2.9.11

    7 months ago

    psycopg2 2.9.11 adds Python 3.14 support, refreshes PostgreSQL 18 error code mappings, and fixes a crash when too many query arguments are passed while Python assertions are enabled. The release also drops Python 3.8 support and modernizes the packaging and CI infrastructure, especially around wheel builds.

    BreakingFeatures

  • 2.9.10

    10/15/2024

    psycopg 2.9.10 adds Python 3.13 support, refreshes PostgreSQL error mappings for PostgreSQL 17, and improves asynchronous notification handling around commits. It also drops Python 3.7 support and modernizes the CI and packaging matrix for newer Python, PostgreSQL, and GitHub Actions versions.

    BreakingFeatures

  • 2.9.9

    10/3/2023

    Release 2.9.9 raises the minimum supported Python version from 3.6 to 3.7 and adds Python 3.12 support. The diff also expands docs and CI to PostgreSQL 16, refreshes documentation build dependencies, and updates release tooling and packaging metadata.

    BreakingFeatures

  • 2.9.8

    9/28/2023

    psycopg2 2.9.8 is mostly a packaging and build update. The main user-visible change is that the binary wheels now bundle PostgreSQL 16 libpq, which enables newer libpq features such as sslcertmode, while the rest of the diff is mostly CI and build script maintenance.

    Features

  • 2.9.7

    8/4/2023

    Psycopg 2.9.7 is a maintenance release focused on fixing module initialization error propagation and making source builds tolerate empty pg_config flags. It also refreshes the wheel build environment, including OpenSSL 1.1.1v and newer build tooling.

    Security

  • 2.9.6

    4/2/2023

    This release is mostly a packaging and build-infrastructure update. The published notes call out new manylinux 2014 wheels for aarch64 and ppc64le, plus a rebuild against OpenSSL 1.1.1t, while the diff shows a broader switch to cibuildwheel and expanded CI wheel matrices.

    SecurityFeatures

  • 2_9_5

    10/25/2022

    This release is mainly a packaging and release-engineering update, with refreshed binary builds and CI to support Python 3.11, OpenSSL 1.1.1r, and PostgreSQL 15 libpq. The only user-facing library behavior called out in the notes is MERGE rowcount support in binary packages.

    Features

  • 2_9_4

    10/6/2022

    The provided input includes only release metadata (version 2_9_4, published 2022-10-06) and does not include any release notes content to analyze. As a result, there is not enough information to identify new features, bug fixes, breaking changes, security updates, or migration guidance for developers.