Feature branches merged to master for 2.8 release - Mailing list psycopg

From Daniele Varrazzo
Subject Feature branches merged to master for 2.8 release
Date
Msg-id CA+mi_8aVzn-4Ujuqg5aMduHjL1XQ3Y7sUU86s3p6shMefaPoSQ@mail.gmail.com
Whole thread Raw
Responses Re: Feature branches merged to master for 2.8 release  (Christian Ferrari <camauz@yahoo.com>)
Re: Feature branches merged to master for 2.8 release  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
List psycopg
Hello,

I've merged most of what I'd like to release for 2.8 into master, so
that I could generate the whole documentation for you to have a look.
The "what's new" [1] in the docs has all the references:

[1] http://initd.org/psycopg/docs/news.html#what-s-new-in-psycopg-2-8

The features are not necessarily finalised in their current forms, so
I'd like to hear from you if you think improvements can be made. The
main points are:

- the new 'errors' module. About it I have a doubt: we convert
postgres error messages [2] from lower_case to CamelCase because the
latter is the convention for Python class, but maybe leaving as they
are makes more sense? Easier to google for them or grep for them in
the postgres sources maybe?
[2] https://www.postgresql.org/docs/current/static/errcodes-appendix.html

- the new properties on 'cursor.description': does it all make sense?

- the new 'connection.info' object: are there other info we could add
or move there? Maybe the new-ish get_dsn_parameters()?

- Anything else?

On the plate for release there is still a couple of small features
(#591: adapting IntEnum right and #782: the capsules) and a bug (#788:
adapting nested empty arrays - aka "the postgres array parser hates
you"). If there is any taker for them you are welcome.

Comments?

Cheers!

-- Daniele


psycopg by date:

Previous
From: Murtuza Zabuawala
Date:
Subject: Re: Adding an informative object to the connection
Next
From: Christian Ferrari
Date:
Subject: Re: Feature branches merged to master for 2.8 release