I think it would be good to keep the usage to read binary data at least.Agreed -- it's only the text file reading I'm proposing to deprecate. It was kind of weird to cram it in there in the first place.Oh, fromfile() has the same issues.ChrisOr is there a good alternative to `np.fromstring(<bytes>, dtype=...)`? -- MartenOn Thu, Oct 22, 2015 at 1:03 PM, Chris Barker <firstname.lastname@example.org> wrote:There was just a question about a bug/issue with scipy.fromstring (which is numpy.fromstring) when used to read integers from a text file.fromstring() is bugging and inflexible for reading text files -- and it is a very, very ugly mess of code. I dug into it a while back, and gave up -- just to much of a mess!So we really should completely re-implement it, or deprecate it. I doubt anyone is going to do a big refactor, so that means deprecating it.Also -- if we do want a fast read numbers from text files function (which would be nice, actually), it really should get a new name anyway.(and the hopefully coming new dtype system would make it easier to write cleanly)I'm not sure what deprecating something means, though -- have it raise a deprecation warning in the next version?