> I have fixed several issues in the lo64 branch. Haven't run the entire test
> grid yet (all supported Py and PG versions, 32 and 64 bits) but modulo
> small tweaks the branch should be ready for integration. However there is
> no chance it can be released in 2.4 or in 2.5 either. What added here is
> the support for an entirely new API, not a bugfix, and its integration has
> added new modes of failure.
Given upstream was unwilling to release this change as part of 2.5, I don't
think we should override them. pyscopg2 is widely used outside of MAAS with a
diverse set of workloads that I don't think we can test.
> Attached is the upstream issue and pull request. /github. com/psycopg/ psycopg2/ pull/259
>
> https:/
Commentary from upstream in the pull request:
> I have fixed several issues in the lo64 branch. Haven't run the entire test
> grid yet (all supported Py and PG versions, 32 and 64 bits) but modulo
> small tweaks the branch should be ready for integration. However there is
> no chance it can be released in 2.4 or in 2.5 either. What added here is
> the support for an entirely new API, not a bugfix, and its integration has
> added new modes of failure.
Given upstream was unwilling to release this change as part of 2.5, I don't
think we should override them. pyscopg2 is widely used outside of MAAS with a
diverse set of workloads that I don't think we can test.