-
Notifications
You must be signed in to change notification settings - Fork 46
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
fix _ProactorEventLoop initialization bug #53
Conversation
`QtCore.QObject.__init__(self)` and `asyncio.ProactorEventLoop.__init__(self, _IocpProactor())` causes double initialization of asyncio.ProactorEventLoop, according to mro. Possibly related to harvimt#38.
@harvimt Do you have a Windows machine to test this on? I don't understand without testing why |
Is it because |
I tested on OS X, AFAICT |
@aknuds1 I tested this on Windows 7 machine with Python 3.4 |
I'm worried that this will be different depending on which Qt implementation is used. |
@harvimt why |
to receive Qt signals, but like I said a better implementation is a On Wed, Nov 18, 2015 at 3:39 AM, Peter Azmanov [email protected]
|
I cherry-picked 847df31, and updated the docstrings so flake8-docstrings stops bugging (new check they added), so this is fixed in master. |
QtCore.QObject.__init__(self)
andasyncio.ProactorEventLoop.__init__(self, _IocpProactor())
causes double initialization of asyncio.ProactorEventLoop, according to mro.Possibly related to #38.