DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 47DC139450FE
To: cygwin@cygwin.com
Subject: Python packaging policy?
Date: Wed, 20 Jan 2021 01:02:14 +0200
Organization: Oleksandr Gavenko <gavenkoa@gmail.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=
From: Oleksandr Gavenko via Cygwin <cygwin@cygwin.com>
Reply-To: Oleksandr Gavenko <gavenkoa@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.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