These are chat archives for numpy/numpy

11th
Jun 2017
Andreas Mueller
@amueller
Jun 11 2017 22:08
@njsmith we fixed the issues in master but not release a couple of month ago, so I think if anyone is to blame it's us ;)
Do you still want to know about the changes? We are testing out master against your nightly built, which should work. We are not testing our release against your nightly built, which I guess we could?
changed behavior here: scikit-learn/scikit-learn#8355 (your issue #8441)
Nathaniel J. Smith
@njsmith
Jun 11 2017 22:13
@amueller: eh, I think that we should be checking our releases against your releases, because we want to know before we finalize a release what will happen when we hit the go button.
Andreas Mueller
@amueller
Jun 11 2017 22:14
It feel us going upstream might be more maintainable? but sure, if you want to put in the effort, we're happy to help in any way
We only needed to patch our tests afaik, so no bugs on user side
(or we would have released yesterday ;)
maybe ask the conda forge people to run this for you?
Nathaniel J. Smith
@njsmith
Jun 11 2017 22:15
I'm not saying I have concrete plans to implement this right now, and if you want to improve yoru testing then by all means go for it :-)
Andreas Mueller
@amueller
Jun 11 2017 22:15
they found the issues
I'm not sure how hard it is for them, but might be easier than for either of us
Nathaniel J. Smith
@njsmith
Jun 11 2017 22:16
I'm just saying, historically when our release manager has done this then the releases went a lot better, and that we do actually want to know about these things
thanks for the links, I'll take a look