From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] python-imaging
Date: Fri, 17 Jul 2020 22:03:31 +0100 [thread overview]
Message-ID: <AM0PR05MB4898591866F28C0088314BD0E77C0@AM0PR05MB4898.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <AM6PR05MB490424B0FD7AC1222ED3EB0DE7610@AM6PR05MB4904.eurprd05.prod.outlook.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1605 bytes --]
On 14/07/2020 15:41, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 10/07/2020 13:24, marco atzeri via Cygwin-apps wrote:
>> 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.
> This worked a treat.
>>>>> 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).
>>>>>
> This also worked really well, thanks for the tip :)
>
>> 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
> Okay. I've updated my test packages, and they are available at
> https://www.hamishmb.com/files/cygwin-temp/ as before. Please let me
> know if I'm now good to go or if there are any more issues.
*bump* in case no one has seen.
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-17 21:03 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
2020-07-14 14:41 ` Hamish McIntyre-Bhatty
2020-07-17 21:03 ` Hamish McIntyre-Bhatty [this message]
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=AM0PR05MB4898591866F28C0088314BD0E77C0@AM0PR05MB4898.eurprd05.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).