Custom Query (121 matches)


Show under each result:

Results (10 - 12 of 121)

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Ticket Resolution Summary Owner Reporter
#25 fixed Constructor and representer for datetimes with timezone do not match xi lele@…

Reported by lele@…, 11 years ago.


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

Reported by Pwipwi, 11 years ago.


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@…

Reported by tim.hochberg@…, 11 years ago.


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()
        return self.represent_mapping(u',2002:map', items)

It might also be convenient to have custom sort orders as PyYaml? legacy does, but that's a bigger change.

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Note: See TracQuery for help on using queries.