On Tue, Jul 9, 2013 at 1:58 PM, Anthony Scopatz <scop...@gmail.com> wrote:

>
>
>
> On Tue, Jul 9, 2013 at 8:57 AM, Tony Yu <tsy...@gmail.com> wrote:
>
>>
>>
>>
>> On Tue, Jul 9, 2013 at 12:58 AM, Antonio Valentino <
>> antonio.valent...@tiscali.it> 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
>>
>>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Pytables-users mailing list
Pytables-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pytables-users

Reply via email to