In fairness, if the process is really exiting, the OS should clear that out.
Even if it is embedded, the embedding process could just release (or zero out)
the entire memory allocation. I personally like plugging those leaks, but it
does feel like putting purity over practicality.
I don't think that sharing data only by copying is the final plan. Proxied
objects seem like a fairly obvious extension.
I am also a bit suspicious of that great timing; perhaps latency is also
important for startup?
___
Python-Dev mailing list --
Hello Mark,
and thanks for your suggestions. However, I'm afraid I haven't explained
our use of python well enough.
On 11/06/2020 12:59, Mark Shannon wrote:
If you need to share objects across threads, then there will be
contention, regardless of how many interpreters there are, or which
Hi Riccardo,
On 10/06/2020 5:51 pm, Riccardo Ghetta wrote:
Hi,
as an user, the "lua use case" is right what I need at work.
I realize that for python this is a niche case, and most users don't
need any of this, but I hope it will useful to understand why having
multiple independent
