On Sat, Jul 26, 2014 at 8:04 PM, Sturla Molden <sturla.mol...@gmail.com> wrote: > Benjamin Root <ben.r...@ou.edu> wrote: > >> My other concern would be with multi-threaded code (which is where a global >> state would be bad). > > It would presumably require a global threading.RLock for protecting the > global state.
We would use thread-local storage like we currently do with the np.errstate() context manager. Each thread will have its own "global" state. -- Robert Kern _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
