Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only mock asyncio on request #525

Merged
merged 1 commit into from
Dec 19, 2023
Merged

Only mock asyncio on request #525

merged 1 commit into from
Dec 19, 2023

Conversation

bblommers
Copy link
Collaborator

Partially reverts #470

Fixes #521
Fixes #522

@marcinsulikowski @boxed As the people that were originally involved with #470 - do you have any problems with this change, to gatekeep this behaviour behind a flag?

The linked issues indicate that this introduced quite some unintended side effects. Hiding this behaviour behind a flag keeps the feature accessible, but also doesn't break everything for others.

I'm torn whether this constitutes a breaking change, or a bugfix. Considering the amount of stuff it seems to break, I may just release it as a new minor version.

@spt29
Copy link

spt29 commented Dec 12, 2023

I would very much appreciate this change: We had literally dozens of failures in our test runs due to the change in behaviour, so I would consider this change here as a bug fix. If one really needs the asyncio stuff, an explicit opt-in looks right. Otherwise pinning to 1.2.2 seems to be the only sane option for us at the moment. 😞

@bblommers bblommers merged commit 3864728 into master Dec 19, 2023
20 checks passed
@bblommers bblommers deleted the gate-asyncio-change branch December 19, 2023 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants