Francesc Alted wrote: > A Monday 21 December 2009 16:31:29 escriguéreu: >>> which is the expected error. In fact, your pytables example works well >>> for me. That's weird... >> It was introduced in a version after 2.6.1, but it's definitely there. >> Here's the bug report I filed, and not only was it confirmed for >> Python 2.7, 3.1, and 3.2 as well, but it's a symptom of a previously >> known bug. >> >> http://bugs.python.org/issue7542 >> http://bugs.python.org/issue7455 >> >> According to the second link, the bug was introduced in May, after >> 2.6.1 came out. >> >> Luckily for us, these were newly generated files, so we can patch them >> and change the C++ code to write "0.0" and not "0" or "0.0". But still >> a parameter might be useful, not only would it give users a way to avoid >> this bug, but it should save the time it takes PyTables to guess whether >> an attribute is a pickled object. > > Okay, let's address this. But instead of using a parameter, I prefer to > implement a case for the "0." string. The ticket (and fix) is in: > > http://pytables.org/trac/ticket/253 > > Of course, this is bad fix in case something would get pickled into a "0.", > but I *strongly* doubt it. > > Thanks for bringing this to my attention!
But it's not just "0.". It also fails with "0". (Which I didn't realize till I read the earlier bug report.) -- Anthony Foglia Princeton Consultants (609) 987-8787 x233 ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Pytables-users mailing list Pytables-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytables-users
