MIME-Version: 1.0
References: 
 <CA+mi_8Y5L-gnio+RUs6XtfOqEbOAiyVS8y9XqYSkfLB8dnPd8w@mail.gmail.com>
 <54a7e6b2-f785-e373-02ca-4fb35f8a9589@aklaver.com>
 <CAMqTPqn2=Vk3Se+ieWgSmgyd8O84G-3-JzUtD1m5M1udfr=6Dg@mail.gmail.com>
 <CACACo5T+PBVTTgAASbEqK6cZQDwKDNSiPvfvCHsKHU3d1_Berg@mail.gmail.com>
 <CANygOGMT+fDUAGUdA7YdYVLoQRV3+3M0foST-F9QsZveoB6DDA@mail.gmail.com>
 <1dfca7ba-f4ed-3c10-87c2-e35e0df8800a@dndg.it>
In-Reply-To: <1dfca7ba-f4ed-3c10-87c2-e35e0df8800a@dndg.it>
From: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: Sat, 26 Jun 2021 12:48:58 +0100
Message-ID: 
 <CA+mi_8bA3Dxw_tJpDt3_oWh8v-Pxpa+6zOFk67ZqE+dp37khYw@mail.gmail.com>
Subject: Re: psycopg is the new psycopg3?
To: Federico Di Gregorio <fog@dndg.it>
Cc: psycopg@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2Bmi_8bA3Dxw_tJpDt3_oWh8v-Pxpa%2B6zOFk67ZqE%2Bdp37khYw%40mail.gmail.com>
Precedence: bulk

On Wed, 11 Nov 2020 at 08:47, Federico Di Gregorio <fog@dndg.it> wrote:

> Reading all the messages I have second toughts. If psycopg2 is here to
> stay, i.e., if it will not be completely replaced by "psycopg3" (and by
> completely I mean shutting down everything about it) then we will have
> the following situation:
>
> psycopg2 version 2.x.y
> psycopg  version 3.w.z
>
> that at first sight is a bit confusing, isn't it?

I have been settled with psycopg3 as the package name for a bit. Then,
a few days ago, releasing psycopg 2.9, I got to see some problems. The
main one is that, in order to respect semver, we should accept
introducing breaking changes only at the change of the main version.
People have been very confused to see breaking changes, although they
were minor, from 2.8 to 2.9.

Semver is much more an accepted, and expected, version number
organisation than having the major number in the package name. I can
expect to see psycopg 4, psycopg 5 etc. as we need to introduce
breaking changes. So I think, although going from psycopg2 v2.x to
psycopg v3.x might be confusing, the need to pin to the minor version
instead of the major is probably more so, and would come to bite us
much more often.

"import psycopg" is ready to merge
(https://github.com/psycopg/psycopg3/commit/7e526af8aca1c31b32a3ad55a0baf0de477c961c)

-- Daniele