From: Tony Yu <ts...@gm...> - 2013-07-09 19:34:27
|
On Tue, Jul 9, 2013 at 1:58 PM, Anthony Scopatz <sc...@gm...> wrote: > > > > On Tue, Jul 9, 2013 at 8:57 AM, Tony Yu <ts...@gm...> wrote: > >> >> >> >> On Tue, Jul 9, 2013 at 12:58 AM, Antonio Valentino < >> ant...@ti...> wrote: >> <snip> >> >> Yes, this is a bug IMO. >>> Thank you for reporting and thank you for the small demonstration script. >>> >>> Can you please file a bug report on github [1]? >>> Please also add info about the PyTables version you used for the test.. >>> >>> >> Thanks for you quick reply. Ticket filed here: >> >> https://github.com/PyTables/PyTables/issues/267 >> > > Thanks Tony, > > I have made my comments on the issue, but the short version is that I > don't think this is a bug, iteration needs a rewrite, and you should use > iterrows(). > > Be Well > Anthony > > PS you should upgrade to 3.0 and use the new API :) > Hey Anthony, Thanks for your thorough response and explanation on the ticket. I closed the ticket, and I'll be using `iterrows` instead of `islice` from now on. I'll have to wait a bit to upgrade to 3.0, but I'm looking forward to getting rid of all the camelCase. Cheers! -Tony > >> >> Best, >> -Tony >> >> > |