Custom Query (121 matches)
Results (10 - 12 of 121)
|#25||fixed||Constructor and representer for datetimes with timezone do not match||xi||lele@…|
I noticed what seems a little glitch in PyYAML handling of datetime when they carry a timezone.
The regexp used to match the various fields assumes there is a separator between the fractional part and the timezone offset, while the representer simply appends the offset without any separator, effectively resulting in a wrong representation (in the case the offset is positive).
Moreover, unicode(data.utcoffset()) gives something like "-1 day, 22:00" for an offset of -2 hours.
|#37||invalid||Cross referenced aliases unsupported ?||xi||Pwipwi|
Hi, the following doesn't work :
- &element1 stuff: "Hey !" link: *element2 # this causes trouble - &element2 stuff: "Ho !" link: *element1
Is it normal, or is it just unsupported for now ? It would be nice to have it :)
|#23||fixed||Dictionary output not sorted.||xi||tim.hochberg@…|
It is convenient to have YAML's output be consistent across runs. Some representers in PyYaml? do this already, but the dictionaries do not. I implemented a quick fix by replacing represent_dict with:
def represent_dict(self, data): items = data.items() items.sort() return self.represent_mapping(u'tag:yaml.org,2002:map', items)
It might also be convenient to have custom sort orders as PyYaml? legacy does, but that's a bigger change.