Backport 2.5 bugfixes

Bug #1304138 reported by Daniele Varrazzo
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
psycopg2 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

[originally posted to psycopg ML: http://www.postgresql.org<email address hidden>]

I've just noticed that the next Ubuntu LTS release will ship with
psycopg rel. 2.4.6, which was the last release in the 2.4 branch.

http://packages.ubuntu.com/source/trusty/psycopg2

In the 2.5 branch, together with a few new features, there have been
several bugs fixed. I've tried backporting these changes to 2.4 and
have found no major problem ("git cherrypick" rocks).

I'm wondering if releasing a 2.4.7 including these bugfixes, together
with the upcoming 2.5.3, would see this package included in the LTS
(maybe not at release time, which I think is imminent, but in a
following update). Has anybody an answer or is more in contact with
Ubuntu release managers to forward them the question?

As a reference, this is the list of fixed issues that would be
included in 2.4.7, if this release would make a sense. Changed code is
in <https://github.com/dvarrazzo/psycopg/tree/maint_2_4>, not pushed
to the official repos yet.

  - Work around `pip issue #1630 <https://github.com/pypa/pip/issues/1630>`__
    making installation via ``pip -e git+url`` impossible (:ticket:`#18`).
  - It is now possible to call `get_transaction_status()` on closed
    connections.
  - Properly cleanup memory of broken connections (ticket #142).
  - Fixed build on Solaris 10 and 11 where the round() function is already
    declared (:ticket:`#146`).
  - Fixed bad interaction of setup.py with other dependencies in
    Distribute project on Python 3 (ticket #153).
  - Meaningful connection errors report a meaningful message, thanks to
    Alexey Borzenkov (:ticket:`#173`).
  - Manually creating `lobject` with the wrong parameter doesn't segfault
    (:ticket:`#187`).
  - Fixed unsafe access to object names causing assertion failures in
    Python 3 debug builds (:ticket:`#188`).
  - Avoid blocking async connections on connect (:ticket:`#194`). Thanks to
    Adam Petrovich for the bug report and diagnosis.
  - Fixed handling of dsn and closed attributes in connection subclasses
    failing to connect (from :ticket:`#192` discussion).
  - Don't segfault using poorly defined cursor subclasses which forgot to call
    the superclass init (:ticket:`#195`).
  - Mark the connection closed when a Socket connection is broken, as it
    happens for TCP connections instead (:ticket:`#196`).
  - Fixed overflow opening a lobject with an oid not fitting in a signed int
    (:ticket:`#203`).
  - Mark the connection closed if found broken on `poll()`.
  - Fixed possible segfault in named cursors creation.
  - Fixed debug build on Windows, thanks to James Emerton.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in psycopg2 (Ubuntu):
status: New → Confirmed
Revision history for this message
Nick Moffitt (nick-moffitt) wrote :

This is similar to bug 1180324 but is a little less "wishlist" than that one, because it lists specific bugs rather than a general desire to see a new version.

Revision history for this message
Daniele Varrazzo (daniele-varrazzo) wrote :

Switching to psycopg 2.5 as per bug 1180324 would supersede this bug (and the 2.4.7 release wouldn't be needed).

Changed in psycopg2 (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.