X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 3682C3947424
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1611118930;
	bh=yC63hICta18qbByepM47sZoxxDsBDtAi80UuogrfQOc=;
	h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=aqJ3wvhX/ibakw4/4ks+X437YI3hzHTcyKG0sLqmG/FAAjRnkN0Mwmd+h8RSLIfX1
	XKqV3ZZcTgSQzK13kqe07tamWrc0SLc0d61imWM9y1hOlLOptRrBjj+13CwKYoTDec
	5watZZB9sxuHk682XmpPyVcNgKnDd+92oHeP4I7A=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 664FA38708F8
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-language
	:content-transfer-encoding;
	bh=RzwgpRdMMvEeN2mFAP7wnzO0Wsld5AhwRmUWvyCdpXo=;
	b=CMNM7dYpmo17yE5HGL3WiiVMkx6IlHx7uVBGGpnqkKW16zd+F37u2STnSCOKnEgk45
	lFwtyY/Xyt7HKELV1mJGitFEiL5wBtjMwo7PjaHd2n6K5a/Xh07/+XY9CU8mULZM4ry3
	MkJmbUkO3a/LywXtemB26GnSQDxaTLGQX2kwXWC8m+pwbRfemFWDp2gM62Lak81NhiYD
	rq6MTj4EGM53mZS7DC3QUgH49hC3CWw8t3PXATiu6mhwjbL5sZrwRT3yjj222Jd8T+gJ
	jrcHLmGd72Tg6bKJvO0tOdraSE3T22IiuIqNfNZRTFE6aYoiNTcX42on6xllb3V6DzmH
	y64g==
X-Gm-Message-State:	AOAM532PmqnAzOiKQj3j/m4kov4WcKWUuejt06nue6ryVi7nTqUz6h6t
	6naAMc9z3Bu1OT4cBqwPd6XoTgEdxG8suQ==
X-Google-Smtp-Source:	ABdhPJyzPx4KesvgkiO/za7NUrPU2loIbUccElEalNJjVZhHnfzAQG+OnSa1Hl/3Pcaa/f/x+tkg3Q==
X-Received:	by 2002:a17:906:2315:: with SMTP id
	l21mr5250221eja.183.1611118926484;
	Tue, 19 Jan 2021 21:02:06 -0800 (PST)
Subject:	Re: Python packaging policy?
To:	cygwin AT cygwin DOT com
References:	<vriuk0s8ledl DOT fsf AT gavenkoa DOT example DOT com>
Message-ID:	<647a2c86-fe44-c044-7d8a-5b47b959f198@gmail.com>
Date:	Wed, 20 Jan 2021 06:02:01 +0100
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
	Thunderbird/78.6.1
MIME-Version:	1.0
In-Reply-To:	<vriuk0s8ledl.fsf@gavenkoa.example.com>
X-Spam-Status:	No, score=-1.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_ASCII_DIVIDERS,
	NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Marco Atzeri via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On 20.01.2021 00:02, Oleksandr Gavenko via Cygwin wrote:
> I figured it out myself that I have to avoid "python3-*" packages and instead
> to work with "python36-*" or "python38-*" as "python3-*" packages are marked
> as "category: _obsolete" in setup.bz2.
> 
> Are there any docs that describes policy for python packages in Cygwin?
> 
> I had experience with https://www.debian.org/doc/packaging-manuals/python-policy/
> That document had answers to the most questions.

Hi Ole,
unfortunately not.
We have not the bandwith to publish official documents as Debian.
As you can see, that document is signed by all the maintainers that
are probably working with python packages.
The current team in Cygwin is one, and I took over from the previous
maintainer when he decided to retire from the project.

I addition Cygwin is a rolling distro so we need to
maintanin some compatibility with the past as we evolve.

> I tried to search for similar information under:
> 
> /usr/share/doc/
> /usr/share/doc/Cygwin
> 
> and in
> 
> git://cygwin.com/git/cygwin-htdocs.git
> 
> and haven't succeeded.
> 
> I'm interested in a package naming/versioning schema, a migration path across
> Python releases and the way of "pip install" to live in harmony with Cygwin.
> 
> I don't insist on anything particular but some "official" generic guide how to
> cook Python in Cygwin would be helpful.

As you can seen from the several python announcements on the
"cygwin-announce" mailing list

https://sourceware.org/pipermail/cygwin-announce/

------------------------------------------------------------
starting from April/June 2020 the work in progress is:

-) update python-2.7, python-3.6, 3.7 and 3.8 at last versions

python-2.7 is officially dead (EOL) upstream so only minor
maintance is performed to "python27-*" packages

python-3.5 is not updated anymore and will be removed in the future.

-) move the meta-package python3 to pull python 3.8 instead of 3.6

The retiring of python 3.6 is not too far, and some subpackages
do not build anymore with it asking for at least 3.7.

-) upload the "python38-*" for the majority of the subpackages
most has been already done.

Currently there are 158 / 159 / 122 packages for python 3.6/3.7/3.8
and most of the difference is in obsoletes packages.

-) work for python 3.9 will start after the rollout of 3.8 is completed.
Probably a summer vacation excercise :-)

-) check the packages still using python 2 and move the major ones to 
3.8 (possibly)

https://sourceware.org/pipermail/cygwin-apps/2021-January/040985.html

-------------------------------------------------------------

About the "pip install" please use 3.8 as your base
and use "python3.8 -m pip .." to avoid misalignment
between python and pip

I plan to convert the test packages to stable

https://cygwin.com/packages/summary/python38.html

by this weekend or next one.
There will be surely some fallout :-(

After the switch or if you are already using the test packages,
if you need to switch between the several python/python3
possibilities, use "alternatives --config ...."

$ alternatives --display python
python - status is auto.
  link currently points to /usr/bin/python3.8
/usr/bin/python3.7 - priority 37
/usr/bin/python2.7 - priority 27
/usr/bin/python3.6 - priority 36
/usr/bin/python3.8 - priority 38
Current `best' version is /usr/bin/python3.8.

$ alternatives --display python3
python3 - status is auto.
  link currently points to /usr/bin/python3.8
/usr/bin/python3.7 - priority 37
/usr/bin/python3.6 - priority 36
/usr/bin/python3.8 - priority 38
Current `best' version is /usr/bin/python3.8.

If you (or others) need other clarification, let me know
on this mailing list and I will try to clarify the matter.

Regards
Marco Atzeri

Cygwin Python maintainer




--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -