Custom Query (121 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (40 - 42 of 121)

Ticket Resolution Summary Owner Reporter
#47 duplicate Cannot compile under gcc version 3.3.5 xi 4rek at poczta onet pl

Reported by 4rek at poczta onet pl, 8 years ago.

Description

gcc version 3.3.5 (Debian 1:3.3.5-13)

Compiler does not recognize '-Wno-pointer-sign' flags

please remove:

AM_CFLAGS = -Wno-pointer-sign

from tests/Makefile.am

#48 wontfix yaml.load does not call __init__ of objects xi aymanbahrain@…

Reported by aymanbahrain@…, 8 years ago.

Description

I noticed that my init code is not called when an object is created via yaml.load. Try this one: In this example, fy.secret will raise an error about secret not an attribute of fy object.

import yaml

class Field:
    def __init__(self):
        print 'init called'
        self.secret = 'password'
        
f = Field()

print f.secret

fy = yaml.load(file('fld.yaml', 'r'))
print fy.hide_value               
print fy.secret

have fld.yaml contain:
!!python/object:__main__.Field 
hide_value: true

#49 fixed yaml confused by python float repr() xi cems a.t. lanl.gov

Reported by cems a.t. lanl.gov, 8 years ago.

Description

platform: intel macintosh, python2.5 , latest yaml.

Description: depending on a floats value dump() will output a different representation format. Sometimes it uses a tag format and others a standard float notation depending on the value.

example:

In [160]:dat ="""
float1: 1.0E-8
float2: 1.0E-9
"""

In [165]:t = yaml.load(dat)

In [166]:t
Out[166]:{'float1': 1e-08, 'float2': 1.0000000000000001e-09}

In [167]:yaml.dump(t)
Out[167]:"{float1: !!float '1e-08', float2: 1.0000000000000001e-09}\n"

notice the !!float tag followed by a string.

regression: this appears to be an attempt to compensate for fact that python's string representation of some float values having different formats: that 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

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 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.)

Note: See TracQuery for help on using queries.