Custom Query (121 matches)

Reported by edemaine@…, 7 years ago.

Example:

>>> import yaml, datetime
>>> yaml.dump(datetime.datetime(2005, 7, 8, 17, 35, 4, 517600))
'2005-07-08 17:35:04.517600\n'
>>> yaml.load(_)
datetime.datetime(2005, 7, 8, 17, 35, 4, 517599)

This breaks the desired rule that yaml.load(yaml.dump(x)) == x in a case where there should be no roundoff. (datetime.datetime uses integers everywhere to avoid any error.)

The offending code seems to be line 321 in yaml/constructor.py:

fraction = int(float(values['fraction'])*1000000)

This seems to be an "easy" way to convert the trailing '.517600' into an integer, but it can go beyond floating-point precision. Wouldn't the following work?

fraction = int(values['fraction'][:6].ljust(6, '0'))

Reported by edemaine@…, 7 years ago.

Could you compile a Windows binary of PyYAML for Python 2.5 (released fairly recently)? Ideally with libyaml support built in...

Reported by roel _ dot _ vanhout _ at _ gmail _ dot _ com, 7 years ago.

2 issues:

• pointer arithmetic on void*'s is a gcc-ism. I 'solved' it by casting them all to a unsigned char (typedef'd), I'm not sure if a unsigned char is guaranteed to be the same size as a void* on all architectures - it worked on 32-bit Windows, FWIW.

• A shorthand struct assignment didn't work, I'm not sure if it's valid C or not but whatever, by writing it out in full it compiled ok.