[Numpy-discussion] NEP: Random Number Generator Policy (original) (raw)

Stephan Hoyer shoyer at gmail.com
Mon Jun 4 00:53:25 EDT 2018

On Sun, Jun 3, 2018 at 8:22 PM Ralf Gommers <ralf.gommers at gmail.com> wrote:

It may be worth having a look at test suites for scipy, statsmodels, scikit-learn, etc. and estimate how much work this NEP causes those projects. If the devs of those packages are forced to do large scale migrations from RandomState to StableState, then why not instead keep RandomState and just add a new API next to it?

Tests that explicitly create RandomState objects would not be difficult to migrate. The goal of "StableState" is that it could be used directly in cases where RandomState is current used in tests, so I would guess that "RandomState" could be almost mechanistically replaced by "StableState".

The challenging case are calls to np.random.seed(). If no replacement API is planned, then these would need to be manually converted to use StableState instead. This is probably not too onerous (and is a good cleanup to do anyways) but it would be a bit of work. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20180603/fcd6ed7c/attachment.html>

More information about the NumPy-Discussion mailing list