On Sun, May 22, 2016 at 2:35 AM, Robert Kern <robert.k...@gmail.com> wrote: > > Well, I mean, engineers want lots of things. I suspect that most engineers > *really* just want to call `numpy.random.seed(8675309)` at the start and > never explicitly pass around separate streams. There's an upside to that in > terms of code simplicity. There are also significant limitations and > constraints. Ultimately, the upside against the alternative of passing > around RandomState objects is usually overweighed by the limitations, so > best practice is to pass around RandomState objects. >
Could we do something like the logging module, and have numpy.random "manage" a bunch of stream objects for you -- so you could get the default single stream easily, and also get access to specific streams without needing to pass around the objects? That would allow folks to start off writing code the "easy" way -- then make it easier to refactor when they realize they need multiple independent streams. -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
