Changes between Initial Version and Version 1 of Ticket #49


Ignore:
Timestamp:
03/22/07 12:14:54 (8 years ago)
Author:
xi
Comment:

Thanks for the suggestion. Fixed in [248].

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #49

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed
  • Ticket #49 – Description

    initial v1  
    2525regression:  
    2626this appears to be an attempt to compensate for fact that python's string representation of some float values having different formats: 
    27 that is in python2.5 the repr() of 1.0e-8  
     27that is in python2.5 the repr() of 1.0e-8 is actually 1e-08 (it supresses the decimal point). Since YAML does not recognize floats without the decimal point the dump command adds the float tag.  However while the repr() of 1.0E-9 is 1.0000000000000001e-09.  which has the decimal point making it legal YAML and it dump avoids the float tag 
    2828 
    29 is actually 1e-08 (it supresses the decimal point). Since YAML does not recognize floats without the decimal point the dump command adds the float tag.  However while the repr() of 1.0E-9 is 1.0000000000000001e-09.  which has the decimal point making it legal YAML and it dump avoids the float tag 
     29It seems to me that a more consistent and desirable result would be obtained if dump were to output 1e-8 as 1.0e-8 rather than using the float if one is parsing a yaml file in another language the tagged format of the float can't be read easily.  (e.g. consider reading this in fortran or perl without using a yaml lib to read the file.) 
    3030 
    31 It seems to me that a more consistent and desirable result would be obtained if dump were to output 1e-8 as 1.0e-8 rather than using the float 
    32  
    33 if one is parsing a yaml file in another language the tagged format of the float can't be read easily.  (e.g. consider reading this in fortran or perl without using a yaml lib to read the file.) 
    34