>> reference counting is not intrusive in CPython (meaning the reference counting structures are outside the PyObject, last I checked) > That's wrong. That was

>> reference counting is not intrusive in CPython (meaning the reference counting structures are outside the PyObject, last I checked) > That's wrong. That was never the case. You are right, I was mistaken. The point stands though, PyObjects are not really an issue for use cases where these tricks are needed. > I was thinking more about a plain fork, like this Right well you can recreate a multiprocessing pool of your own with different pros and cons, sure, that's an other approach I guess.