public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Daniele Varrazzo <[email protected]>
To: Federico Di Gregorio <[email protected]>
Cc: [email protected]
Subject: Re: psycopg is the new psycopg3?
Date: Sat, 26 Jun 2021 09:52:03 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+mi_8bA3Dxw_tJpDt3_oWh8v-Pxpa+6zOFk67ZqE+dp37khYw@mail.gmail.com>
References: <CA+mi_8Y5L-gnio+RUs6XtfOqEbOAiyVS8y9XqYSkfLB8dnPd8w@mail.gmail.com>
<[email protected]>
<CAMqTPqn2=Vk3Se+ieWgSmgyd8O84G-3-JzUtD1m5M1udfr=6Dg@mail.gmail.com>
<CACACo5T+PBVTTgAASbEqK6cZQDwKDNSiPvfvCHsKHU3d1_Berg@mail.gmail.com>
<CANygOGMT+fDUAGUdA7YdYVLoQRV3+3M0foST-F9QsZveoB6DDA@mail.gmail.com>
<[email protected]>
<CA+mi_8bA3Dxw_tJpDt3_oWh8v-Pxpa+6zOFk67ZqE+dp37khYw@mail.gmail.com>
On 6/26/21 4:48 AM, Daniele Varrazzo wrote:
> On Wed, 11 Nov 2020 at 08:47, Federico Di Gregorio <[email protected]> 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.
Somewhere you lost me in the above.
What exactly is the proposed package naming and versioning going to be
going forward?
>
> "import psycopg" is ready to merge
> (https://github.com/psycopg/psycopg3/commit/7e526af8aca1c31b32a3ad55a0baf0de477c961c)
>
> -- Daniele
>
>
--
Adrian Klaver
[email protected]
view thread (19+ 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], [email protected], [email protected]
Subject: Re: psycopg is the new psycopg3?
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