Psycopg

Latest version: v3.2.3

Safety actively analyzes 681844 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 8

3.1.6

^^^^^^^^^^^^^

- Fix `cursor.copy()` with cursors using row factories (:ticket:`460`).

3.1.5

^^^^^^^^^^^^^

- Fix array loading slowness compared to psycopg2 (:ticket:`359`).
- Improve performance around network communication (:ticket:`414`).
- Return `!bytes` instead of `!memoryview` from `pq.Encoding` methods
(:ticket:`422`).
- Fix `Cursor.rownumber` to return `!None` when the result has no row to fetch
(:ticket:`437`).
- Avoid error in Pyright caused by aliasing `!TypeAlias` (:ticket:`439`).
- Fix `Copy.set_types()` used with `varchar` and `name` types (:ticket:`452`).
- Improve performance using :ref:`row-factories` (:ticket:`457`).

3.1.4

^^^^^^^^^^^^^

- Include :ref:`error classes <sqlstate-exceptions>` defined in PostgreSQL 15.
- Add support for Python 3.11 (:ticket:`305`).
- Build binary packages with libpq from PostgreSQL 15.0.

3.1.3

^^^^^^^^^^^^^

- Restore the state of the connection if `Cursor.stream()` is terminated
prematurely (:ticket:`382`).
- Fix regression introduced in 3.1 with different named tuples mangling rules
for non-ascii attribute names (:ticket:`386`).
- Fix handling of queries with escaped percent signs (``%%``) in `ClientCursor`
(:ticket:`399`).
- Fix possible duplicated BEGIN statements emitted in pipeline mode
(:ticket:`401`).

3.1.2

^^^^^^^^^^^^^

- Fix handling of certain invalid time zones causing problems on Windows
(:ticket:`371`).
- Fix segfault occurring when a loader fails initialization (:ticket:`372`).
- Fix invalid SAVEPOINT issued when entering `Connection.transaction()` within
a pipeline using an implicit transaction (:ticket:`374`).
- Fix queries with repeated named parameters in `ClientCursor` (:ticket:`378`).
- Distribute macOS arm64 (Apple M1) binary packages (:ticket:`344`).

3.1.1

^^^^^^^^^^^^^

- Work around broken Homebrew installation of the libpq in a non-standard path
(:ticket:`364`)
- Fix possible "unrecognized service" error in async connection when no port
is specified (:ticket:`366`).

Page 4 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.