yjq added the comment:
https://github.com/aio-libs/aiohttp/issues/3202#issuecomment-439644135
--
versions: -Python 3.6
___
Python tracker
<https://bugs.python.org/issue34
yjq added the comment:
I'm sure that this should be a bug in python. But because I'm naive, I'm not
sure about how to fix it. I think we can just add the exception to
base_events._FATAL_ERROR_IGNORE.
--
___
Python
Change by yjq :
--
title: Fatal error on SSL transport -> Fatal read error on socket transport
___
Python tracker
<https://bugs.python.org/issue34148>
___
_
yjq added the comment:
Other people also found this in a year. And asvetlov already pull requests. But
no one cares about this at all!
https://community.home-assistant.io/t/announcement-appdaemon-3-0/47394/56
https://github.com/aio-libs/aiokafka/issues/344
https://github.com/conjure-up
yjq added the comment:
I'm using python 3.7.2. And I met the same problem.
--
nosy: +yjqiang
___
Python tracker
<https://bugs.python.org/issue33350>
___
___
yjq added the comment:
updated: I tried the test.py and it didn't show this error. So I think what I
got is not the same problem as issue33350 although it shows the same traceback
message.
--
___
Python tracker
<https://bugs.py
New submission from yjq :
Fatal read error on socket transport
protocol:
transport: <_SelectorSocketTransport fd=47 read=polling write=>
Traceback (most recent call last):
File
"/var/containers/Bundle/Application/9F565D30-C54B-4210-902B-874D7A5AB814/Pythonista3.app/Frameworks/Py3Ki
yjq added the comment:
More information:
https://github.com/omz/Pythonista-Issues/issues/555
--
___
Python tracker
<https://bugs.python.org/issue34148>
___
___
Change by yjq :
--
nosy: -asvetlov, yselivanov
___
Python tracker
<https://bugs.python.org/issue34148>
___
___
Python-bugs-list mailing list
Unsubscribe:
