public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Python 3.9
Date: Sun, 2 Jan 2022 14:04:26 +0000	[thread overview]
Message-ID: <DB3PR0202MB3561CA12FE154AC624125EDFE7489@DB3PR0202MB3561.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <7cb92521-6e55-d37d-6d5c-2ba0b2898cf0@gmail.com>

On 31/12/2021 11:45, Marco Atzeri wrote:
> On 28.12.2021 11:12, Hamish McIntyre-Bhatty wrote:
>> On 28/12/2021 07:17, Marco Atzeri wrote:
>>> On 27.12.2021 00:14, Hamish McIntyre-Bhatty wrote:
>>>> On 25/12/2021 07:19, Marco Atzeri wrote:
>>>>>
>>>>> I think the "test" limitation is not needed.
>>>>>
>>>>> Regards
>>>>> Marco
>>>>
>>>> Perhaps, but I need to sort the unit tests, they won't even compile 
>>>> right now.
>>>
>>> Testing Imaging with "tox"
>>> 1 failed, 1868 passed, 43 skipped, 4 xfailed, 3 warnings
>>>
>>> I need to repeat with X for some of the skipped tests.
>>>
>>> Few additional module are needed for the test and I am packing them.
>>
>> Oh, I was talking about python3-wx and wxWidgets-3.1. python-imaging's 
>> built in tests work fine, but there are only like 50 of them IIRC.
>>
>> Let me know how that goes and I'll update the package to test with tox 
>> when "cygport test" is run, if that seems like a good idea. I need to 
>> update it anyway because the CI failed to built it for some reason.
>>
> 
> tox and the others needed for python-imaging tests are up.
> 
> Up to you if you want to add the "test" phase or not to the cygport.
> Currently almost none of the python packages have a proper testing;
> I locally used pytest or tox for testing them
> 
> Regards
> Marco

Cheers, I'll have a look.

What command(s) are you using to test with tox? I have never used tox 
before so it would be useful to know.

Hamish

  reply	other threads:[~2022-01-02 14:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09  6:26 Marco Atzeri
2021-12-12 22:14 ` Marco Atzeri
2021-12-13 11:52   ` Hamish McIntyre-Bhatty
2021-12-13 12:32   ` Hamish McIntyre-Bhatty
2021-12-13 18:29     ` Marco Atzeri
2021-12-17 18:34   ` Hamish McIntyre-Bhatty
2021-12-17 18:35   ` Hamish McIntyre-Bhatty
2021-12-25  7:19     ` Marco Atzeri
2021-12-26 23:14       ` Hamish McIntyre-Bhatty
2021-12-28  7:17         ` Marco Atzeri
2021-12-28 10:12           ` Hamish McIntyre-Bhatty
2021-12-31 11:45             ` Marco Atzeri
2022-01-02 14:04               ` Hamish McIntyre-Bhatty [this message]
2022-01-02 16:00                 ` 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=DB3PR0202MB3561CA12FE154AC624125EDFE7489@DB3PR0202MB3561.eurprd02.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).