Custom Query (121 matches)
Results (67 - 69 of 121)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #70 | worksforme | really slow on large input ... | xi | lal.george@… |
| Description |
yaml.load appears to be really (really) slow on large input. My string is
Both the input and output are fairly simple. Why does it take a long time to parse? Lal |
|||
| #73 | invalid | numpy arrays ... | xi | lal.george@… |
| Description |
What is the best way to transfer very large numpy arrays using PyYAML? Ideally I would like to do something like:
However, the yaml.load returns an exception:
Since I have quoted the string, yaml should not be diving into it - correct? Thanks. Best,
|
|||
| #25 | fixed | Constructor and representer for datetimes with timezone do not match | xi | lele@… |
| Description |
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. |
|||
