David Parks added the comment:
Having a flag seems like a good solution to me. I've also encountered this
issue and posted on stack overflow about it here:
https://stackoverflow.com/questions/62748654/python-3-8-shared-memory-resource-tracker-producing-unexpected-warnings-at-
David Parks added the comment:
An answer came in over the stack overflow question.
https://stackoverflow.com/questions/58019939/attributeerror-str-object-has-no-attribute-errno/58084380#58084380
The issue is that OSError implements a custom __reduce__ function which needs
to be override by
David Parks 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
Change by David Parks :
--
title: Pickle not deserializing an OSError exception as expected -> Pickle not
deserializing an aiohttp ClientConnectorError exception as expected
___
Python tracker
<https://bugs.python.org/issu
New submission from David Parks :
Below is a minimum reproducible test case of what appears to be an issue in
pickle.
Before pickling the exception ClientConnectionError, from aiohttp, the property
ClientConnectionError._os_error is a PermissionError object (a subclass of
OSError). After
David Parks added the comment:
Oh yes, this belongs to aiohttp. I thought that was handled here. I'll move
this to a git issue on that page, and I'm closing this.
https://github.com/aio-libs/aiohttp/issues/4077
--
resolution: -> rejected
stage: -> resolved
status
David Parks added the comment:
Minor correction to the minimal reproducible test case:
```
import multiprocessing
import aiohttp
connection_key = aiohttp.client_reqrep.ConnectionKey
ose = OSError('test')
e = aiohttp.client_exceptions.ClientConnectorError(connection_k
New submission from David Parks :
Original question posted here:
https://stackoverflow.com/questions/58019939/attributeerror-str-object-has-no-attribute-errno?noredirect=1#comment102443264_58019939
The following exception is encountered when placing an
