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.

Sign up for GitHub

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

Jump to bottom

bluez: Allow accessing Bleak from multiple individual event loops (not simultaneously) #1031

Closed
wants to merge 1 commit into from
Closed

bluez: Allow accessing Bleak from multiple individual event loops (not simultaneously) #1031

wants to merge 1 commit into from

Commits on Sep 26, 2022

  1. bluez: Allow accessing Bleak from multiple individual event loops 

    Previous event loop needs to be closed for this to work, as the rest
of the DBus access code doesn't support concurrent access from more than one
MessageBus instance.

However this allows creating per-test Bleak classes with pytest-asyncio that
don't overlap each other, and possibly other use cases as well.
    @projectgus
    projectgus committed Sep 26, 2022
    Configuration menu
    Copy the full SHA
    d00aaf4 View commit details
    Browse the repository at this point in the history