Gremlin Python 3.4.13 - Exception Ignored Message When Existing A Python Main
What Happens
This happens in Gremlin Python 3.4.13
Traceback (most recent call last):
File "C:\Python310\lib\asyncio\proactor_events.py", line 116, in del
self.close()
File "C:\Python310\lib\asyncio\proactor_events.py", line 108, in close
self._loop.call_soon(self._call_connection_lost, None)
File "C:\Python310\lib\asyncio\base_events.py", line 750, in call_soon
self._check_closed()
File "C:\Python310\lib\asyncio\base_events.py", line 515, in _checkclosed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
client.close()
# Let the underlying cleanup for a bit.
for in range(5):
sleep(0.25)
`
Seems to avoid the error.
This happens in Gremlin Python 3.4.13
- Open
self.connection = DriverRemoteConnection(url, 'g') - Run some Gremlin Queries
- Close
self.connection.close() - Exit the Main immediately after the close().
After Exception ignored in: <function _ProactorBasePipeTransport.del at 0x000001CB0D9232E0>Traceback (most recent call last):
File "C:\Python310\lib\asyncio\proactor_events.py", line 116, in del
self.close()
File "C:\Python310\lib\asyncio\proactor_events.py", line 108, in close
self._loop.call_soon(self._call_connection_lost, None)
File "C:\Python310\lib\asyncio\base_events.py", line 750, in call_soon
self._check_closed()
File "C:\Python310\lib\asyncio\base_events.py", line 515, in _checkclosed
raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed
**What I Was Expecting**
Because I closed it, I would expect no above error should be raised.
May be I am doing this wrong, or there may need to be additional config or set up that I am missing.
** Workaround **
client.close()
# Let the underlying cleanup for a bit.
for in range(5):
sleep(0.25)
`
Seems to avoid the error.
