Hi Barry
You wrote:
We need to define terms here. What do you mean by permanent?
Good question. I think I answered it in my original post:
An object is transient if it can be garbage collected. An object is permanent if it will never be garbage collected.
Aha. Ok that what I think of as rarely modified and only shared by forking.
You also wrote:
Being able to create python share object files is another problem.
At the level I'm working at, that's what might unkindly be called an implementation detail. It is in fact a very important matter. But a simple-minded implementation would be enough to produce a proof-of-concept.
It's a huge design problem. There are no simple PoC's that come to my mind.
I think I am showing how what you want, if I have not misunderstood, could be implemented.
Oh, that's very good. In my original post my focus was on explaining as clearly as I could the basic concepts. For that reason (and others) I said little about implementation. If you like, I'd be very happy to discuss implementation with you and others, either here or on the Python C-API list.
The reason that this is a problem in the first place is an implementation detail...
Barry
However, I'd like to put that off for a few days. And this would give others on this list an opportunity to comment.
--
Jonathan