I don't think I have the bandwidth but I agree :-/
Not sure if any of the other core devs do. I can try to read it next
week but that's probably too late?
On 06/19/2018 02:34 AM, Robert Kern wrote:
On 6/16/18 00:59, Robert Kern wrote:
I have made a significant revision. In this version, downstream
projects like scikit-learn should experience significantly less
forced churn.
https://github.com/rkern/numpy/blob/nep/rng-clarification/doc/neps/nep-0019-rng-policy.rst
https://mail.python.org/pipermail/numpy-discussion/2018-June/078252.html
The screaming has died down on numpy-discussion, and it seems like
everyone who has participated over there has more or less come to
consensus about accepting this NEP. However, I'd really appreciate it
if I could get some kind of feedback from a scikit-learn dev, whether
it's "I don't care" or "I need a couple of days to get around to
reading the NEP" or just "+1" or "-1000; this is awful!"
I'm not picky.
_______________________________________________
scikit-learn mailing list
scikit-learn@python.org
https://mail.python.org/mailman/listinfo/scikit-learn
