From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: python 2 check & cleaning
Date: Mon, 18 Jan 2021 12:16:51 +0100 [thread overview]
Message-ID: <5ea5278e-1d68-34cd-9e53-8a6222cac94f@gmail.com> (raw)
In-Reply-To: <4e2b7b2f-0a94-0723-77a2-f9fddf905a6d@SystematicSw.ab.ca>
On 18.01.2021 08:21, Brian Inglis wrote:
> On 2021-01-17 22:33, Marco Atzeri via Cygwin-apps wrote:
>> Could you please check your packages if they will work with
>> preferred python3.8?
>
> @ units
> ...
> requires: cygwin findutils libreadline7 python3 python36 python36-requests
> ...
> depends2: cygwin, findutils, libreadline7, python36, python36-requests
> build-depends: autoconf, binutils, coreutils, cygport, cygwin-devel,
> gawk, gcc-core, grep, libncurses-devel, libreadline-devel, perl_base,
> python3, python3-devel, python3-requests, sed, texinfo
>
> $ head -1 `which units_cur`
> #!/usr/bin/python3.6m
>
> How can I ensure units depends2 and requires, and the script hash-bang
> uses only the generic python3, python3-devel, python3-requests like
> build-depends, and avoids using the "current" specific version 36/3.6m?
Hi Brian,
python3-requests for the time being will pull python36-requests.
That is fine for your
#!/usr/bin/python3.6m
Cygport has hard coded the OBSOLETES, this is something
we need to change in cygport:
>>> python36-requests OBSOLETES: python3-requests
> And how can I ensure that units_cur is tested using only python38 modules?
> Will the hash-bang override the command line run python38 `which
> units_cur`?
>
rebuilding from your source I had
units requires: cygwin findutils libreadline7 python38 python38-requests
It seems the "inherit python3" is pulling the current choice
of my system
$ 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.
Regards
Marco
next prev parent reply other threads:[~2021-01-18 11:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 5:33 Marco Atzeri
2021-01-18 7:21 ` Brian Inglis
2021-01-18 11:16 ` Marco Atzeri [this message]
2021-01-18 20:58 ` Brian Inglis
2021-01-18 18:25 ` Ken Brown
2021-01-19 15:10 ` Ken Brown
2021-01-19 15:39 ` Marco Atzeri
2021-01-18 22:28 ` Lemures Lemniscati
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=5ea5278e-1d68-34cd-9e53-8a6222cac94f@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@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).