[issue38254] Pickle not deserializing an aiohttp ClientConnectorError exception as expected

[David Parks]

David Parks <davidparks21 at gmail.com> added the comment:

I may be wrong here, but the issue appears to be a problem in pickle, which is why I brought it over here. From the looks of the very simple code in the Exception I can't see that there's any way that this exception is possible unless pickle itself has a bug. Pickle appears to be reconstructing the object with a string in a place where an Object was before the serialization process.

The issue is currently reported under aiohttp here: https://github.com/aio-libs/aiohttp/issues/4077

It's also posted (originally) on stack overflow here: https://stackoverflow.com/questions/58019939/attributeerror-str-object-has-no-attribute-errno

----------
resolution: third party -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38254>
_______________________________________