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