On 11/1/14, Alan G Isaac <alan.is...@gmail.com> wrote: > On 11/1/2014 4:41 PM, Alexander Belopolsky wrote: >> I cannot think of a situation where I would need more generality such as >> reading every 3rd row or rows with the given numbers. Such processing is >> normally done after the text data is loaded into an array. > > > I have done this as cheaper than random selection for a quick and dirty > look at large data sets. Setting maxrows can be very different if the > data has been stored in some structured manner. > > I suppose my view is something like this. We are considering adding a > keyword. > If we can get greater functionality at about the same cost, why not? > In that case, it is not really useful to speculate about use cases. > If the costs are substantially greater, then that should be stated. > Cost is a good reason not to do something. >
`slice_rows` is a generalization of `max_rows`. It will probably take a bit more code to implement, and it will require more tests and more documentation. So the cost isn't really the same. But if it solves real problems for users, the cost may be worth it. Warren > fwiw, > Alan Isaac > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
