A Thursday 25 November 2010 14:38:00 Gerrit Holl escrigué: > Hi, > > On 25 November 2010 09:09, Francesc Alted <fal...@pytables.org> wrote: > > Yes, the behaviour in PyTables is the expected one (and it is > > document correctly too). I think the reason for this was some > > lazyness on my part: I wanted to share the code between the > > `read()` method and `iterrows()`. That being said, I agree that > > it would be better if `iterrows()` would expose your suggested > > behaviour. > > I see; array.read(12345) is the same as array.read(start=12345) and > that's why stop=start+1... > > I missed that piece of documentation, it says "If you only want to > iterate over a given range of rows in the array, you may use the > start, stop and step parameters, which have the same meaning as in > Array.read()" and clearly I didn't read on to that one. > > > However, I'm not sure if we should change the current behaviour > > because that may broke some existing code. In fact, my vote would > > go for keeping backwards compatibility. What others think? > > I agree that it's better to keep a sub-optimal solution than to break > backwards compatibility, unless the major version changes (Pytables > 3? :P). [clip]
I agree with that. PyTables 3 would be a nice time for implementing this. Please mention that in the ticket. Thanks, -- Francesc Alted ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
