From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: python fails asyncio tests (py 3.7 & 3.8)
Date: Mon, 7 Dec 2020 19:14:44 -0800 [thread overview]
Message-ID: <2732c01b-fdd2-c677-841f-5c1b2a5c07f5@maxrnd.com> (raw)
In-Reply-To: <f5c9f51a-1d4b-cb0a-d648-2abfed220651@gmail.com>
Marco Atzeri via Cygwin wrote:
> On 07.12.2020 08:58, Mark Geisert wrote:
>> [Replying to myself...]
>>
>> Mark Geisert wrote:
>>> Jim Bell wrote:
>>>> On 2020-11-21 5:59 AM, Jim Bell wrote:
>>>>> The standard python asyncio tests hang.
>>>>>
>>>>> cd /usr/lib/python3.8/test
>>>>>
>>>>> python3.8 test_asyncore.py -v
>>>>>
>
>> As for the test script errors you reported, I can submit a workaround patch that
>> would make its way into the Python3.8 tests. I am unsure at the moment which
>> Cygwin package contains those tests but I can figure that out. Otherwise, I
>> could tell you what needs to be patched in test_asyncore.py and you could edit
>> the script yourself to fix this locally for yourself.
>>
>> Let me know how you'd like to proceed, when you have a chance.
>
> test_asyncore.py is part of the test suite of python itself.
> I doubt patching the test will change the functionality of the program itself
I agree. I guess I was looking for some input from OP on what direction would be
most useful to him. If he'd like a workaround patch directly in order to make
progress sooner on whatever direction he's going, I can provide it. Otherwise I
would engage with the Python maintainer /* pause, looks up maintainer, oh Hi
Marco! */ to get the patch into Cygwin's Python package(s) for future release in
due course.
Regards,
..mark
prev parent reply other threads:[~2020-12-08 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 11:59 Jim Bell
2020-11-22 0:13 ` Jim Bell
2020-12-01 0:53 ` Mark Geisert
2020-12-07 7:58 ` Mark Geisert
2020-12-07 18:01 ` Marco Atzeri
2020-12-08 3:14 ` Mark Geisert [this message]
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=2732c01b-fdd2-c677-841f-5c1b2a5c07f5@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@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).