Strange output

[nayab9]

As far as I can tell, instawow is working as expected. It will list all my addons and it will update them too; the only strange part is the following output after it completes tasks:

Exception ignored in: <function _ProactorBasePipeTransport.__del__ at 0x03ECF8E0>
Traceback (most recent call last):
  File "c:\users\varian\appdata\local\programs\python\python38-32\lib\asyncio\proactor_events.py", line 116, in __del__
    self.close()
  File "c:\users\varian\appdata\local\programs\python\python38-32\lib\asyncio\proactor_events.py", line 108, in close
    self._loop.call_soon(self._call_connection_lost, None)
  File "c:\users\varian\appdata\local\programs\python\python38-32\lib\asyncio\base_events.py", line 715, in call_soon
    self._check_closed()
  File "c:\users\varian\appdata\local\programs\python\python38-32\lib\asyncio\base_events.py", line 508, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

Any ideas what this output is? It doesn't seem to be negatively impacting the usage of instawow from what I can tell.

[layday]

This is (was) a latent bug in aiohttp, the networking library I'm using. What would previously cause an innocuous ResourceWarning manifests as an exception in Python 3.8 on Windows. It will be fixed in the next version of aiohttp. You are correct that this does not interrupt other operations but I'll think about what (if anything) I can do to work around the issue until the fix is published.

See https://bugs.python.org/issue39232 and aio-libs/aiohttp#4324 for the gory details.

[nayab9]

Thanks for the info! Will continue using either way, cannot live without instawow!

P.s. do you have an Ethereum or Bitcoin Cash adress so I can buy you a beer? 🍻

[layday]

Afraid not but thanks for offering!

[layday]

I decided to take the easy route and force 3.8 to use the 3.7 loop. I'll release a new version of instawow containing the fix later today.

[layday]

Fixed in v1.7.1.