Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcYMU-0006JN-IS for psycopg@arkaria.postgresql.org; Tue, 10 Nov 2020 18:27:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kcYMS-0007Ic-Ll for psycopg@arkaria.postgresql.org; Tue, 10 Nov 2020 18:27:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcYMR-0007IV-JI for psycopg@lists.postgresql.org; Tue, 10 Nov 2020 18:27:19 +0000 Received: from mail-vs1-xe33.google.com ([2607:f8b0:4864:20::e33]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kcYML-0002AD-3q for psycopg@postgresql.org; Tue, 10 Nov 2020 18:27:18 +0000 Received: by mail-vs1-xe33.google.com with SMTP id u7so7627969vsq.11 for ; Tue, 10 Nov 2020 10:27:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VXEMjdHKgqgUv7cIsSeT1iWn9T/ky99uu6r7amwfekY=; b=N3k1nvp7mtjPDV5xh17IkC1fnVrwkNMWNifilqSuqSabJkUsO4KZ/FhJF+y8aHRAjE dp2OInwMnE+VIxLqPZlJ9+KYVc4aQztLvOUPNCliFzAoti7SnGibsEMqXYKGMHxtrb98 Z9HPtbC1YRMbS3DXaqcI4ey3JeBVDiuCrWfUmKW1KeRMZMzPdrpXFTkR+fB8d7+KppcZ DV+bio/2sL5gMeLyqAI2TFCWLwiTpmWtR6l7bRJ/9lzP9L1ef2+oZxfas1AoivDzLFZ+ L/s7icpGUkGxG9mLKXJGPgk5WoqBEJnrFFp74bA8+rSlUmJoZSLGe2QdZ73n2/5wLY2E hiJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VXEMjdHKgqgUv7cIsSeT1iWn9T/ky99uu6r7amwfekY=; b=pxOnqnVL4asJGYZAiJa7RMT9AUO9cAQzYdLEX/+hN9qg6vZZsEhaloyDyZk7SeWxsa F8URZd/71wQDb2h6Z64T6aJRjGRyaWrQNzurr9wWH6kVBb8ZI34R+uI2IXwFZaksiZ/l z59sK/+3Lkjf93q12aPR8uDSzUhGbiBJ9d3uk2CCyLaI9lm83S3+0ohKp9QNbVk1PzIh SZA5FuaQa8DZ1OBiAavjz59ruR9pwJQtgT2sv8a94IQb+yFARjkLWbB17jOQOCKNjElI R4TXcOWs5ms2Wanz8og1FrHUURCj9BiyNtvt7pJUIYKmJ+Co+L66ck3EgJogv7dALWQP S3wA== X-Gm-Message-State: AOAM531zfgu1ZS5bcXak4QqK4f10JgwT/Rdt9Eowj+h6sbm8+i1yK2eB NWBuFnN2BAluKr7CVU8pMZFgeRMMOIaciOyThdw= X-Google-Smtp-Source: ABdhPJwz3EHcD/YRPquGJSHFwU1E+kLEGfj13GsrdzUlUAMvs/xy5G7ppNMYXSG70TWKehJnY0kyRybNDnQRcAe7mKc= X-Received: by 2002:a67:fc87:: with SMTP id x7mr5827066vsp.56.1605032831910; Tue, 10 Nov 2020 10:27:11 -0800 (PST) MIME-Version: 1.0 References: <54a7e6b2-f785-e373-02ca-4fb35f8a9589@aklaver.com> In-Reply-To: <54a7e6b2-f785-e373-02ca-4fb35f8a9589@aklaver.com> From: Vladimir Ryabtsev Date: Tue, 10 Nov 2020 10:27:01 -0800 Message-ID: Subject: Re: psycopg is the new psycopg3? To: Adrian Klaver Cc: Daniele Varrazzo , psycopg@postgresql.org Content-Type: multipart/alternative; boundary="000000000000cc872405b3c4d3a8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000cc872405b3c4d3a8 Content-Type: text/plain; charset="UTF-8" As long as psycopg2 is not disappearing anywhere, psycopg3 seems better. New users will interpret psycopg2 as "more advanced psycopg". Vladimir On Tue, 10 Nov 2020 at 10:06, Adrian Klaver wrote: > On 11/10/20 9:12 AM, Daniele Varrazzo wrote: > > Hello, > > > > I have received some concerned voices in regard to have a package called > > "psycopg3". I guess many have been burned out by the Python 2 to 3 > > transition, and now it's not a happy pair of number to see next to each > > other. Sorry, Fibonacci... > > > > The rationale behind having the 2 in the package name was to allow the > > coexistence between v1 and 2. But now that nobody uses v1 anymore, I > > think the name can be considered free. I believe it even predates pypi > > and the requirements.txt convention. Dark times... > > > > Anyone against using "psycopg" as package name, and starting from 3 as > > version number? > > Yes. > > 1) "psycopg" is widely used as an alias for psycopg2, so that will cause > confusion. > > 2) I see a lot of explaining why the order of versions is psycopg2, > psycopg. > > 3) People don't seem to be confused that you can use psycopg2 with both > Python 2 and 3. > > > > > Cheers, > > > > -- Daniele > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > > --000000000000cc872405b3c4d3a8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As long as psycopg2 is not disappearing anywhere, psycopg3= seems better.
New users will interpret psycopg2 as "more advanced= psycopg".

Vladimir

On Tue, 10 Nov 2020 = at 10:06, Adrian Klaver <ad= rian.klaver@aklaver.com> wrote:
On 11/10/20 9:12 AM, Daniele Varrazzo wrote:
> Hello,
>
> I have received some concerned voices in regard to have a package call= ed
> "psycopg3". I guess many have been burned out by the Python = 2 to 3
> transition, and now it's not a happy pair of number to see next to= each
> other. Sorry, Fibonacci...
>
> The rationale behind having the 2 in the package name was to allow the=
> coexistence between v1 and 2. But now that nobody uses v1 anymore, I <= br> > think the name can be considered free. I believe it even predates pypi=
> and the requirements.txt convention. Dark times...
>
> Anyone against using "psycopg" as package name, and starting= from 3 as
> version number?

Yes.

1) "psycopg" is widely used as an alias for psycopg2, so that wil= l cause
confusion.

2) I see a lot of explaining why the order of versions is psycopg2, psycopg= .

3) People don't seem to be confused that you can use psycopg2 with both=
Python 2 and 3.

>
> Cheers,
>
> -- Daniele


--
Adrian Klaver
adrian.klave= r@aklaver.com


--000000000000cc872405b3c4d3a8--