fix _ProactorEventLoop initialization bug

[peterazmanov]

QtCore.QObject.__init__(self) and asyncio.ProactorEventLoop.__init__(self, _IocpProactor()) causes double initialization of asyncio.ProactorEventLoop, according to mro.
Possibly related to #38.

[aknuds1]

@harvimt Do you have a Windows machine to test this on? I don't understand without testing why asyncio.ProactorEventLoop would get double initialized though.

[aknuds1]

Is it because QObject calls super().__init__() that asyncio.ProactorEventLoop gets double initialized? Difficult to tell without testing.

[aknuds1]

I tested on OS X, AFAICT QObject does indeed call super().__init__() so that the next baseclass (ProactorEventLoop) gets initialized twice. So, in summing up, looks good to me.

[peterazmanov]

@aknuds1 I tested this on Windows 7 machine with Python 3.4

[harvimt]

I'm worried that this will be different depending on which Qt implementation is used.
I suggest moving the object that can receive the signal into it's own object instead of subclassing QObject and ProactorEventLoop like I do in #29.

[peterazmanov]

@harvimt why _ProactorEventLoop (or any class in the quamash.QEventLoop hierarchy) needs inheritance from QObject? AFAICT, unix implementation is different in this regard.

[harvimt]

to receive Qt signals, but like I said a better implementation is a
dedicated signal receiver object.

On Wed, Nov 18, 2015 at 3:39 AM, Peter Azmanov notifications@github.com
wrote:

@harvimt https://github.com/harvimt why _ProactorEventLoop (or any
class in the quamash.QEventLoop hierarchy) needs inheritance from QObject?
AFAICT, unix implementation is different in this regard.

—
Reply to this email directly or view it on GitHub
#53 (comment).

[peterazmanov]

@harvimt PyQt successfully connects signals to methods of non-QObject-subclass class. PyQt docs

[harvimt]

Sorry not receive or send, but declare.
Only EventPoller needs to be a QObject, I fix this in 847df31, (which is part of #29, which I never merged)

[harvimt]

I cherry-picked 847df31, and updated the docstrings so flake8-docstrings stops bugging (new check they added), so this is fixed in master.