[issue21553] Behaviour of modules depends on how they where imported

2014-05-22 Thread mythsmith
New submission from mythsmith: I found a condition where different behaviour could be observed depending on how a module is imported. It seems to be different to write: import module # against: from package import module In the attachment you find a minimal package (imptest) with this

[issue20660] Starting a second multiprocessing.Manager causes INCREF on all object created by the first one.

2014-02-19 Thread mythsmith
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

[issue20660] Starting a second multiprocessing.Manager causes INCREF on all object created by the first one.

2014-02-19 Thread mythsmith
mythsmith 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? Anyway, I cannot upgrade right now. Would it be an option to subclass BaseProxy, override the _after_fork

[issue20660] Starting a second multiprocessing.Manager causes INCREF on all object created by the first one.

2014-02-17 Thread mythsmith
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