This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author davin
Recipients davin, njs, pitrou, sbt, yselivanov
Date 2017-03-16.20:50:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489697418.62.0.938069230832.issue29828@psf.upfronthosting.co.za>
In-reply-to
Content
Having a read through issue16500 and issue6721, I worry that this could again become bogged down with similar concerns.

With the specific example of NumPy, I am not sure I would want its random number generator to be reseeded with each forked process.  There are many situations where I very much need to preserve the original seed and/or current PRNG state.

I do not yet see a clear, motivating use case even after reading those two older issues.  I worry that if it were added it would (almost?) never get used either because the need is rare or because developers will more often think of how this can be solved in their own target functions when they first start up.  The suggestion of a top-level function and Context method make good sense to me as a place to offer such a thing but is there a clearer use case?
History
Date User Action Args
2017-03-16 20:50:18davinsetrecipients: + davin, pitrou, njs, sbt, yselivanov
2017-03-16 20:50:18davinsetmessageid: <1489697418.62.0.938069230832.issue29828@psf.upfronthosting.co.za>
2017-03-16 20:50:18davinlinkissue29828 messages
2017-03-16 20:50:18davincreate