public inbox for [email protected]
help / color / mirror / Atom feedFrom: Aryeh Leib Taurog <[email protected]>
To: [email protected]
To: [email protected]
Subject: Re: Feature branches merged to master for 2.8 release
Date: Mon, 15 Oct 2018 21:27:26 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CA+mi_8aVzn-4Ujuqg5aMduHjL1XQ3Y7sUU86s3p6shMefaPoSQ@mail.gmail.com>
<[email protected]>
<CA+mi_8bRgi5rFZbnVAiDLK_B-ZLNa-ze9uK6y3WONHu_zq1u_Q@mail.gmail.com>
<[email protected]>
I also think CamelCase should be preferred for consistency with
accepted Python standards. It seems to me that if the exception
string representation includes the PostgreSQL snake_case name (perhaps
in parentheses), that should be sufficient for any reference needs,
because it will appear in the message printed with the traceback.
Usually if I want to search for more information about an error, I
just paste that into my browser.
Also, I wouldn’t be surprised if google is smart enough to handle the
switch between camel case and snake case, but I haven’t tested it.
In any case, this is an exciting and welcome addition to an already
excellent library. Thanks much for all your efforts.
> On Mon, Oct 15, 2018 at 06:23:57PM +0100, Daniele Varrazzo wrote:
>
view thread (20+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Feature branches merged to master for 2.8 release
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox