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 gvanrossum
Recipients ajoino, alex.gronholm, asvetlov, chris.jerdonek, dreamsorcerer, gvanrossum, iritkatriel, jab, njs, tinchester, yselivanov
Date 2022-02-21.03:35:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1645414526.93.0.652170686947.issue46771@roundup.psfhosted.org>
In-reply-to
Content
[Alex]
> The current backward incompatible changes in cancellation behavior are already causing 10 tests to fail in the AnyIO test suite. I'm trying to find an alternate solution that does not break anything.

Are you sure that the tests aren't over-specified? Maybe you could link to the failing test run? (Though I worry that understanding your test infrastructure might be a bit much.)

That said, when I landed this change I wasn't at all sure that it wouldn't break things (there just weren't any asyncio tests that it broke), and I am totally willing to roll that part back or change it if it breaks a valid use case.

So basically I am saying please chill, feature freeze isn't until late May.
History
Date User Action Args
2022-02-21 03:35:26gvanrossumsetrecipients: + gvanrossum, njs, jab, asvetlov, alex.gronholm, chris.jerdonek, yselivanov, tinchester, iritkatriel, dreamsorcerer, ajoino
2022-02-21 03:35:26gvanrossumsetmessageid: <1645414526.93.0.652170686947.issue46771@roundup.psfhosted.org>
2022-02-21 03:35:26gvanrossumlinkissue46771 messages
2022-02-21 03:35:26gvanrossumcreate