On Oct 7, 2010, at 3:49 PM, Benjamin Root wrote: > > I understand the technicalities of why this occurs, but from a user's > perspective, he is asking for distinct numpy arrays of specified types. The > transposing seems to be almost an unimportant implementation detail because > the user is asking for the data to be split up by columns. Personally, I > think that this should be transparent to the user and should be able to work > -- although I am not exactly sure if one should just simply return a list of > numpy arrays with the column names dropped, or a list of one-column record > arrays.
Well, easy enough to output a list of arrays for each column, be they of the same dtype or with different ones. > If it can't quite work from within the framework for genfromtxt/loadtxt, then > maybe another text loading function that is designed to have the data format > known a priori would be suitable? Not needed. The unpack argument is used as the very end of the function anyway. Anyhow, could you open a ticket to that effect (else I'm quite likely to forget about it). > Note that such a function might also be sufficient in addressing my > long-standing qualm with loadtxt()'s squeeze behavior for files with only one > line of data. Mind opening a second a ticket ? _______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
