Mark Harviston

Sorry for the misunderstanding, you want to do precisely the opposite of what I thought. Someone else wanted to do this and the recommendation was to wrap everything in `asyncio.async`...

QtCore.QEventLoop isn't a second event loop, it's a second "view" of the same event loop. check the code for PR #11, it uses QtCore.QEventLoop to do it's thing. On Fri,...

yeah. that could be a problem, the obvious solution is to have each run of `run_until_complete()` wrap a `QtCore.QEventLoop`, that might be wise, or a seperate inline_async function, but I...

Note that the failing appveyor tests (kinda) pass. py.test is returning an exit status that isn't zero, but the console output shows all tests pass. I'm able to replicate this...

the test-2019 branch mostly works, but hasn't been tested thoroughly. On Sun, Sep 22, 2019 at 4:07 AM hivemall wrote: > so pyside2 dead for quamash, @harvimt will > there...

this looks like it's working as expected. The wizard closes, then the application quits because all windows attached to the application are closed, but the asyncio loop attached to the...

This is now a sort of feature request that's essentially a duplicate of #33. In all cases so far there's been a workaround, but nested execs are a thing people...

I re-read this and I will need to investigate further.

hrm. I'm not able to reproduce (I'm on Mac OS X using python 3.5.2 and PyQt5.6) I'll try on windows and linux when I get home.

replicated on windows. In all cases the problem is that the loop exits when all windows are closed, so a dummy window that keeps the app open and the do...