Hi Ralf, Sorry not to have recalled the previous thread.
Your point about not doing things in the python 2->3 move makes sense; handy for me is no reason to give users an incentive not to move to python3 because their matrix-dependent code breaks. It does sound like, given the use of sparse, a separate package - or perhaps (temporary) inclusion in scipy - would be the way to go. In turn, collecting as much of the matrix tests and work-arounds together in the `matrixlib` would be the right first step. And, even better, to collect thoughts in a NEP. Now if only I had not written this while procrastinating on other things... All the best, Marten _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
