➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pablogsal
Recipients Anthony Sottile, Mark.Shannon, gvanrossum, nedbat, pablogsal, petr.viktorin
Date 2021-05-04.16:12:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1620144742.61.0.681878275777.issue43933@roundup.psfhosted.org>
In-reply-to
Content 
> The pytest failure still happens with 3.10.0b1 and pytest 6.2.3.

What I am missing? 3.10.0b1 includes the fixes for this issue, no? Is it because the fixes still require some changes in the source? If that's the case, we should mention it in the What's New

> I'm asking if pytest can make a release to update.

In any case, shouldn't that be requested in the pytest issue tracker?
History
Date User Action Args
2021-05-04 16:12:22pablogsalsetrecipients: + pablogsal, gvanrossum, nedbat, petr.viktorin, Mark.Shannon, Anthony Sottile
2021-05-04 16:12:22pablogsalsetmessageid: <1620144742.61.0.681878275777.issue43933@roundup.psfhosted.org>
2021-05-04 16:12:22pablogsallinkissue43933 messages
2021-05-04 16:12:22pablogsalcreate