(Apologies for the slow reply, I'm in the middle of a relocation
at the moment so e-mail access isn't consistent, and will be a
lot worse over the next few weeks.)
On Tue, Jul 10, 2018 at 07:31:49AM -0700, David Foster wrote:
> I was not aware of PyParallel. The PyParellel "paralle
MRAB wrote:
The shared object's refcount would be incremented and the sharing
function would return a proxy to the shared object.
Refcounting in the thread/process would be done on the proxy.
When the proxy is closed or garbage-collected, the shared object's
refcount would be decremented.
W
> On 17 Jul 2018, at 20:35, Eric Snow wrote:
>
>> On Mon, Jul 16, 2018 at 11:08 AM Antoine Pitrou wrote:
>> On Mon, 16 Jul 2018 18:00:37 +0100
>> MRAB wrote:
>>> Could you explicitly share an object in a similar way to how you
>>> explicitly open a file?
>>>
>>> The shared object's refcount
On Tue, Jul 17, 2018 at 1:44 PM Barry wrote:
> The decrement itself is not the problem, that can be made thread safe.
Yeah, by using the GIL. Otherwise, please elaborate. My
understanding is that if the decrement itself were not the problem
then we'd have gotten rid of the GIL already.
> Do y
On Mon, Jul 16, 2018 at 11:08 AM Antoine Pitrou wrote:
> On Mon, 16 Jul 2018 18:00:37 +0100
> MRAB wrote:
> > Could you explicitly share an object in a similar way to how you
> > explicitly open a file?
> >
> > The shared object's refcount would be incremented and the sharing
> > function would r
