From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: cygwin@cygwin.com
Subject: Python packaging policy?
Date: Wed, 20 Jan 2021 01:02:14 +0200 [thread overview]
Message-ID: <vriuk0s8ledl.fsf@gavenkoa.example.com> (raw)
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/
next reply other threads:[~2021-01-19 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 23:02 Oleksandr Gavenko [this message]
2021-01-20 5:02 ` Marco Atzeri
2021-01-20 10:26 ` Hamish McIntyre-Bhatty
2021-01-20 13:15 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vriuk0s8ledl.fsf@gavenkoa.example.com \
--to=gavenkoa@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).