> Decoupled or not, sparse still needs to be dealt with. What is the plan? >
My view would be: - keep current sparse matrices as is (with improvements, like __numpy_func__ and the various performance improvements that regularly get done) - once one of the sparse *array* implementations progresses far enough, merge that and encourage people to switch over - in the far future, once packages like scikit-learn have switched to the new sparse arrays, the sparse matrices could potentially also be split off as a separate package, in the same way as we did for weave and now can do for npmatrix. I think that's the best way forward as well. This can happen independently of numpy matrix changes, and doesn't leave users with silently broken code.
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
