R. David Murray added the comment:
Based on Richard's comments I'm closing this won't fix. If someone comes up
with a clever solution, we can reopen.
--
nosy: +r.david.murray
resolution: - wont fix
stage: - resolved
status: open - closed
___
Richard Oudkerk added the comment:
Thanks Richard. The set_start_method() call will affect any process
started from that time on? Is it possible to change idea at some point in
the future?
You can use different start methods in the same program by creating different
contexts:
spawn_ctx
mythsmith added the comment:
That would probably mean that proxy objects could not be inherited by *any*
sub-process.
If I only avoid after-fork incref, I must be very careful at not deleting them
in any subprocess, as this would cause a decref which was not compensated by
the after-fork
Richard Oudkerk added the comment:
On Unix, using the fork start method (which was the only option till 3.4),
every sub process will incref every shared object for which its parent has a
reference.
This is deliberate because there is not really any way to know which shared
objects a
New submission from mythsmith:
I seems that upon the start of a second manager, all objects referenced in the
first one gets an INCREF. On the third start, all objects created by the first
and the second manager get another INCREF. And so on. I cannot understand why
the start of a totally new
Changes by Ned Deily n...@acm.org:
--
nosy: +sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20660
___
___
Python-bugs-list mailing list
