On Thu, Oct 22, 2015 at 5:47 PM, Chris Barker - NOAA Federal <chris.barker@noaa.gov> wrote:

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.

Chris

Or is there a good alternative to `np.fromstring(<bytes>, dtype=...)`? -- Marten

On Thu, Oct 22, 2015 at 1:03 PM, Chris Barker <chris.barker@noaa.gov> 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.

https://mail.scipy.org/pipermail/scipy-user/2015-October/036746.html

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?

There was discussion at SciPy 2015 of separating out the text reading abilities of Pandas so that numpy could include it. We should contact Jeff Rebeck and see about moving that forward.

Chuck