Subject: Re: psycopg is the new psycopg3?
To: Daniele Varrazzo <daniele.varrazzo@gmail.com>, psycopg@postgresql.org
References: 
 <CA+mi_8Y5L-gnio+RUs6XtfOqEbOAiyVS8y9XqYSkfLB8dnPd8w@mail.gmail.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
Message-ID: <54a7e6b2-f785-e373-02ca-4fb35f8a9589@aklaver.com>
Date: Tue, 10 Nov 2020 10:05:57 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.4.2
MIME-Version: 1.0
In-Reply-To: 
 <CA+mi_8Y5L-gnio+RUs6XtfOqEbOAiyVS8y9XqYSkfLB8dnPd8w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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