X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org AEA6A3945056
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1611097345;
	bh=ymVLuVnOsgfWnLPfTnK5JNLpJ3fmQIeCiAgyWzlGiz8=;
	h=To:Subject:Date:List-Id:List-Unsubscribe:List-Archive:List-Post:
	List-Help:List-Subscribe:From:Reply-To:From;
	b=ImtH+axi6PLkqrw8qzLY/6kjCMDQsbc6dsE8bl1U80Ui++1Mje1EF7NY/+SalkuAL
	NAWNkv4U0MLy+pMxx4eyKA2mca+/ANxyMOlL0YX+6S1QxnCeiTpzXjU/zx0u2l/owQ
	5occJgMn9SI92siQicG1Ba6NCn2YMltYyO37cVtk=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 47DC139450FE
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
Subject:	Python packaging policy?
Date:	Wed, 20 Jan 2021 01:02:14 +0200
Organization:	Oleksandr Gavenko <gavenkoa AT gmail DOT com>, http://defun.work/
Message-ID:	<vriuk0s8ledl.fsf@gavenkoa.example.com>
Mime-Version:	1.0
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/27.1 (cygwin)
Cancel-Lock:	sha1:AURlP8TRxTsoF9VjBLWYiD88wp0=
X-Spam-Status:	No, score=3.9 required=5.0 tests=BAYES_00, DKIM_ADSP_CUSTOM_MED,
	FORGED_GMAIL_RCVD, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,
	HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, KAM_GENERICHEALTH,
	KAM_OTHER_BAD_TLD, NML_ADSP_CUSTOM_MED, PDS_OTHER_BAD_TLD, SPF_HELO_NONE,
	SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Level:	***
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-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:	Oleksandr Gavenko via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Oleksandr Gavenko <gavenkoa AT gmail DOT com>
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

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.

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.

-- 
http://defun.work/

--
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 -