From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] python-imaging
Date: Fri, 10 Jul 2020 14:24:55 +0200 [thread overview]
Message-ID: <CAB8Xom85XQhfHfkx8L6fPh-ZUR+f=w_dKya-W-h6nQy-cg3FJQ@mail.gmail.com> (raw)
In-Reply-To: <AM6PR05MB4904E10BFE87A4A4ED2B8447E7650@AM6PR05MB4904.eurprd05.prod.outlook.com>
On Fri, Jul 10, 2020 at 12:28 PM Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>
> On 10/07/2020 01:20, airplanemath via Cygwin-apps wrote:
> >> I tend to use loops like
> >>
> >> for ver in ${PYTHON_WHEEL_VERSIONS//:/ };
> >> do
> >> /usr/bin/python${ver} script
> >> done
> >>
> >> for the tests. Also, I believe ${ARCH} is the same as $(uname -m) here,
> >> if you want to streamline the PYTHONPATH definition a bit. Both of
> >> those are personal style and you are entirely welcome to ignore this.
> Originally it was using a loop like that for the tests, but for some
> reason not all of the Python versions I wanted to build for were being
> tested that way (it was only doing 3.7 and 3.8). I figure I might as
> well use ARCH then, makes it a bit clearer.
> >> Other than that, I noticed you're writing your own src_compile and
> >> src_install. Is there some reason python_wheel_compile and
> >> python_wheel_install aren't working for you? I haven't noticed a problem
> >> with either of those functions in the past year or so. (For reference, the
> >> value of PYTHON_WHEEL_VERSIONS determines which python versions
> >> are compiled: see
> >> https://cygwin.github.io/cygport/python-wheel_cygclass.html#robo361).
>
> Ah, thank you for that link, that clears things up for me. I didn't
> realise I could do that. So, I can just set PYTHON_WHEEL_VERSIONS to
> "3.6:3.7:3.8" to build for those versions? I guess I don't need the
> custom functions that way, that would make things simpler.
>
> So far I've built for Python 3.6 and newer, should I also be building
> for 3.5 or are we not bothered at this point?
I am not bothering with 3.5 for my builds.
The focus should be to have 3.8 up and running
so 3.6:3.7:3.8 are enough
>
> >> Thank you for taking up this package.
>
> You're welcome, and thanks for the advice :)
>
> Hamish
Regards
Marco
next prev parent reply other threads:[~2020-07-10 12:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 14:59 Hamish McIntyre-Bhatty
[not found] ` <136eb766-af71-c758-186b-fd9c98214642@aol.com>
2020-07-10 0:20 ` airplanemath
2020-07-10 10:26 ` Hamish McIntyre-Bhatty
2020-07-10 12:24 ` marco atzeri [this message]
2020-07-14 14:41 ` Hamish McIntyre-Bhatty
2020-07-17 21:03 ` Hamish McIntyre-Bhatty
2020-07-17 21:11 ` Brian Inglis
2020-07-17 21:25 ` Marco Atzeri
2020-07-18 20:07 ` Marco Atzeri
2020-07-19 16:36 ` Hamish McIntyre-Bhatty
2020-07-19 17:09 ` Marco Atzeri
2020-07-19 17:26 ` Hamish McIntyre-Bhatty
2020-07-19 19:09 ` Marco Atzeri
2020-07-21 16:04 ` Hamish McIntyre-Bhatty
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='CAB8Xom85XQhfHfkx8L6fPh-ZUR+f=w_dKya-W-h6nQy-cg3FJQ@mail.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).