On Tuesday 12 May 2009 21:16:11 Mark Fenner wrote: > In a message from January 2009, an LRU cache problem in the Pro > version seemed to > pop up: > > Original message here: > http://www.mail-archive.com/pytables-users%40lists.sourceforge.net/msg01081 >.html > > I've come across the same issue (though presumably with different > data). Weird, weird, weird. The query succeeds when hardcoded > (tbl.where('my query here")) but fails when part of a string > expression (tbl.where("my query"+str(variable)+"more query")). It > only fails for one value of variable. > > I'm using the evaluation pro version. Has this, perhaps, been > addressed in recent patches to the pro version (which, incidentally, > I'm just about ready to pull the trigger on once I get funding).
Yes, the problem with the optimized LRU cache was fixed and the patch was included in the latest release of PyTables Pro (2.1.1), together with some other fixes and enhancements. See: http://www.pytables.org/moin/ReleaseNotes/Release_2.1.1 for more info. Regards, -- Francesc Alted ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users