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 1g8P2Q-00055J-TV for psycopg@arkaria.postgresql.org; Fri, 05 Oct 2018 12:16:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g8P2P-0006Lq-5B for psycopg@arkaria.postgresql.org; Fri, 05 Oct 2018 12:16:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g8P2P-0006Lj-0G for psycopg@lists.postgresql.org; Fri, 05 Oct 2018 12:16:57 +0000 Received: from mout.gmx.net ([212.227.17.22]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1g8P2M-0003hz-GE for psycopg@lists.postgresql.org; Fri, 05 Oct 2018 12:16:56 +0000 Received: from hermes ([84.165.100.166]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MHso5-1g9EWE37Kn-003aOu for ; Fri, 05 Oct 2018 14:16:52 +0200 Received: from hermes ([84.165.100.166]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MHso5-1g9EWE37Kn-003aOu for ; Fri, 05 Oct 2018 14:16:52 +0200 Received: from ncq by hermes with local (Exim 4.91) (envelope-from ) id 1g8P2I-00068l-Iq for psycopg@lists.postgresql.org; Fri, 05 Oct 2018 14:16:50 +0200 Date: Fri, 5 Oct 2018 14:16:50 +0200 From: Karsten Hilbert To: psycopg@lists.postgresql.org Subject: Re: Plans for 2.8 Message-ID: <20181005121650.GC5215@hermes.hilbert.loc> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Ma_X_il-Followup-to: d Re_X_turn-receipt-to: Karsten.Hilbert@gmx.net Di_X_sposition-Notification-To: Karsten.Hilbert@gmx.net X-Confi_X_rm-Reading-To: Karsten.Hilbert@gmx.net X-Pri_X_ority: 2 (High) User-Agent: Mutt/1.10.1 (2018-07-13) Sender: X-Provags-ID: V03:K1:MqWUOMcewkQj2np/zxuNjla2IArrD6d7V4I893FM7N1IWKIr8kq wGlessxBCWEArSRCB/9WfLs4dD1qYDhRVDg0pBWar25yInfEifGJsD7A4hluWhmRe2z+/b+ lcWn3Q/ExwQduL/5AHaA1bFRD9kyzlzH7vJAnoB+SKerOiXFN0tlaxQ27fssfffoT//fs93 AW+/9bjeSAWiK43UpyACg== X-UI-Out-Filterresults: notjunk:1;V01:K0:O6nr09C10vU=:9MgH8zRmXQgp+2VBUTedyf 8tr+gr6tGzUo+EtLop3vGG6wg1I5yBY5r8a9u5W4vRNLJAHAzDTf9qli0i9CmWjFoDWOBfycM ouZXqbsdcCW2hBnxqWv4zfvYdtb7c3Tp5FPBXaZPK7YxPMUXJnGdecxMohTjai/bdUkES1hgD SzJlQ0upV4bkkGOs5vlB/Dy9FVSwkNNNYNffsk4Koku+82U3+tdkuxD3tHtoKoQDmDOdYVhsC 7KUibcce0Yvzuu1g/t30Onoup7xxOPjF9Ivq5woIrPTNSw85tL+qn/QTF1frpnTnvw0TPvUNy ZooSVwqIRduKnUbbvj27MT1IBwLTqeYovs8ArVsT5+j8iqqepJVn4NJjYCagwgT0/xVmSaHvW khwGlviMS2BM/Z0bD5BYcKT6I2laTRpp3KGTjG0xo4L0ItS+11eBop5Qz6gPZ2yKc8T2tcz5O IMs0dUNFOQsmPjvPbs5ql43x8RGPXGa2ccvHvZSKq8rsCDUq9NsM7/bb3M0NOMi1Pq+4K2rtJ 2fsN/pOi0LDTAGNBcbRwRyFAe8bXFlUmGFcQ2wez4Wzhut2qi3yXub+1TLyS35wTNntm51xKC idq5ouiWO50ZcpELmBz/GWh4pay4dJ8U64E1e31K1omlyua38jGWFFSjpSKdg0JzWiAT2/nW1 lFB9RA2oYoo2atAMsmxXrLZa77dxUs9GYfVFMrVw+atiWOXfOb4SVJdc9XImxFOuxE4ek1D4A zTPdMw8HJCWyI6vDGbJbNNDyGe3Vhkfa/vjp1EeyOLSaQxtuMQCK8KlndRTf7apFs+3uiEZ0i 81QWjkGkq/siPCm3WU5MO+uvxE1FA== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Oct 04, 2018 at 01:38:03PM +0100, Daniele Varrazzo wrote: > [2] https://github.com/psycopg/psycopg2/blob/master/NEWS > > The feature I'm the most excited about (and worried about its > reception) is to raise a different exception for every postgres error > message (see #682). You needn't as far as I'm concerned because as long as this > The error classes are [...] subclasses of the previously existing ones is true there should not be a problem. Will the new classes still have .pgcode set to their respective values ? Thanks, Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B