From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: Tox issues with Python 3.6 and 3.7
Date: Fri, 4 Feb 2022 07:48:06 +0100 [thread overview]
Message-ID: <a1815fc4-7184-97af-9a1c-ea33b2719070@gmail.com> (raw)
In-Reply-To: <AM0PR0202MB35557F6A22E26588FF432DE2E7289@AM0PR0202MB3555.eurprd02.prod.outlook.com>
On 03.02.2022 20:34, Hamish McIntyre-Bhatty wrote:
> On 20/01/2022 14:56, Hamish McIntyre-Bhatty wrote:
>> Hi there,
>>
>> This is a follow-up to Marco Atzeri and I talking about tox in the
>> Python 3.9 email thread. I have just started trying to use tox for
>> testing python-imaging.
>>
>> I have found that tox has some issues on Python 3.6 and 3.7, namely that:
>>
>> 3.6:
>>
>> Marco, I assume you didn't have these problems when you tested, or you
>> found a way to fix them. Having never used tox before, I'm at a bit of
>> a loss, any ideas?
>>
>> Hamish
>>
>>
> *Bump* as it seems this slipped past everyone's radar.
>
> Hamish
Hi Hamish,
just very low on my priority list
if you pass the test on 3.9 is already enough for me
Regards
Marco
prev parent reply other threads:[~2022-02-04 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 14:56 Hamish McIntyre-Bhatty
2022-02-03 19:34 ` Hamish McIntyre-Bhatty
2022-02-04 6:48 ` Marco Atzeri [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=a1815fc4-7184-97af-9a1c-ea33b2719070@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).