-
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
Windows Errors #38
Comments
I also have these errors, in my app and in my tests, when closing the event loop :
Debugging with pycharm, here is what I found. But then, in https://github.com/python/asyncio/blob/7baef9de28bd0a8e5bb14ad962059dced9f23bb3/asyncio/windows_events.py#L718, there remains for some reason a future calling as a callback "QEventLoop._loop_self_reading" in the cache, and is pending. This future is then canceled. It's descriptor is different from the previous one ( adress : 133875744 ) but an error is present on this one : 997. |
This pull request was doing a regression. The logs in this issue are not present, but with my patch they come back. |
`QtCore.QObject.__init__(self)` and `asyncio.ProactorEventLoop.__init__(self, _IocpProactor())` causes double initialization of asyncio.ProactorEventLoop, according to mro. Possibly related to harvimt#38.
The PyQt4 and PyQt5 tests on appveyor are passing, but I get this:
may be related to #34
PySide tests give off a similar error, in addition to:
but fail, however, the PySide tests have been failing for awhile for no reason on windows (like the tests all pass, but the exit code of py.test is non-zero)
The text was updated successfully, but these errors were encountered: