Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gC1Xf-0005WY-3i for psycopg@arkaria.postgresql.org; Mon, 15 Oct 2018 12:00:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gC1Xd-0005MB-1p for psycopg@arkaria.postgresql.org; Mon, 15 Oct 2018 12:00:09 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gC1Xc-0005M3-Pr for psycopg@lists.postgresql.org; Mon, 15 Oct 2018 12:00:08 +0000 Received: from sonic310-12.consmr.mail.ir2.yahoo.com ([77.238.177.33]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gC1XZ-0006EI-BP for psycopg@postgresql.org; Mon, 15 Oct 2018 12:00:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1539604802; bh=XlUokt359hCtbZRTu5H5F0rLsmDtbNygQc1TIYbMNxA=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=DVguaF04XQqgWfwJddFSnGpiEvVi5xjLEsTqIyauusyKFJ9tlD7f3W+AdIQfnn1nGfbtwi1oBX8WKXvu4JT0L2qeOSvSF7ifIN1QWnP/n7use2p0tDaeaMut6T4UIiyts+90TcplhP4rFSyHGdgEvHDOqHRFQZCZx+kCRLH5aAY0NgCtxvROOmKpXMIwnRFjAIJ7x6blSBzx8yAId7zUDbwKD8V0+GkZqOVrJRQXbgId7IAc91pdibemqmJYU8gncgfKkEvH1mAHfOm02qSL3v0lP63eMgsEC3Y/xWJC86aJOMhNNj9hTal2omAUvoHffKLShOxxVRDrbmC4icVmEQ== X-YMail-OSG: A42_oe4VM1lj11qKwqCd4VpAP_m18jByOJ8F8W8FrTa3eWYt.xtx3Aske3JdrjX 4ICD1csYVML3iGEUNQXDhP3Ht03AS4_YSyUY4OvpM8O2YZi.Q_z0OgxwYa_mFi3t12D8zicisYd3 G32R44SkY_9f1YcgD1pa.saFIzp5UKYj_trAqNtZSNf4j48hIqIbJjdSrnM7qk5Q0Wybx6AgfASF fZIgrq0HfcWyOZjdphwuF1C4yecaipyZ0DiMmKp8P88FK2QQurugdrEsJ4HM2PHPTC39DcJm6YvJ 0VgQgQHpqw7PIOcfFeLp20jIyReG4Nx9S5lG8jRR_vnuiYtPmdArmwWm1UyGpf.wVozHUDDH1IdK OEt4SIowIZ94ba2RQlQikhyWURhvRJvCOf1LrFkub_vvop0b3JHgHQPcSNSlMwBp0.xcmmLetWIk 58xj95UVmSv3e_0hoqKiHqubcs_xPgy5hqtG1iJHtt9RpTn7JCWeTFN18xiKiQIh6CRnbmBcIItD .6T3VCcWwJkH2Qm68m41FWN1bTI._3jb1Zo5eClS8zEzayOipSfkveDSs7pslJrmnxm5Nz3FtUB3 lpYzkuVlIQnP8OmFJhMWiFiAta5ro7m5Q1bZMkYuKDfLACCaM_iuTJZgIKUFxkvKAqj48MOsoIi. fO4V_2zntPqaIZzlFJ2IsEM.1RR545LPxRBkobp.1nSckijVjOHRL.i2At__acdYRnYlOR14QFwA 8CpiCFy6zTDixEdmEHflnrFJUZ4.ghSZ22cSfjRR_ZYVV9xLwxThbrAfg9Hof4RG7fTP3bmJiojY XTUQhmayqy40uJ387T1M.UMddMXHokdy58sbMJb557kHs1SvUfw82ql602zRZ7tOMU2bx1CNvynf a6tODTzD27hhBp.2rCwr8ymMSSXRttItbhZu0KmR5.0BmoU3XSe4nJsSZZoNMvJyQxbJ.iro4I.u EEIgBQI.zdcpLUgnpM.Y8OsE3XEGzMsxRtbbujoSKNCJy0MpPOUsYqMKB4Vbl15EoyfB0RStddKD mPZLdRNSlne.GRI0- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.ir2.yahoo.com with HTTP; Mon, 15 Oct 2018 12:00:02 +0000 Date: Mon, 15 Oct 2018 11:59:57 +0000 (UTC) From: Christian Ferrari Reply-To: Christian Ferrari To: psycopg@postgresql.org Message-ID: <1878453370.14916776.1539604797985@mail.yahoo.com> In-Reply-To: References: Subject: Re: Feature branches merged to master for 2.8 release MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_14916775_1781615556.1539604797982" X-Mailer: WebService/1.1.12512 YMailNorrin Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Content-Length: 5605 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_14916775_1781615556.1539604797982 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Daniele,what about the "_get_native_connection()" ?RegardsCh.F. ------------------------------------------------------------- Good design can't stop bad implementation =20 Il luned=C3=AC 15 ottobre 2018, 13:48:24 CEST, Daniele Varrazzo ha scritto: =20 =20 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 =20 ------=_Part_14916775_1781615556.1539604797982 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Daniele,
what about the "_get_native_connection()= " ?
Regards
Ch.F.

--------------------------------------------------------= -----
Good design can't stop bad impl= ementation


=20
=20
Il luned=C3=AC 15 ottobre 2018, 13:48:24 CEST, Daniele = Varrazzo <daniele.varrazzo@gmail.com> ha scritto:


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:

The features are not necessarily fin= alised in their current forms, so
I'd like to hea= r 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 beca= use 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
th= e postgres sources maybe?

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

- the new 'connection.info'= object: are there other info we could add
or mov= e there? Maybe the new-ish get_dsn_parameters()?
=
- Anything else?

<= /div>
On the plate for release there is still a couple of s= mall features
(#591: adapting IntEnum right and #= 782: the capsules) and a bug (#788:
adapting nest= ed empty arrays - aka "the postgres array parser hates
you"). If there is any taker for them you are welcome.

Comments?
=
Cheers!

-- Daniele

------=_Part_14916775_1781615556.1539604797982--