Custom Query (121 matches)
Results (70 - 72 of 121)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #85 | fixed | PyYaml don't have a version | xi | miki@… |
| Description |
There is currently no way I could find to detect the current version of PyYaml? I'm using. There should be a __version__ in the top level yaml module |
|||
| #86 | wontfix | Use on socket connections with non blocking flag set | xi | oscar.ostlund@… |
| Description |
I am trying to use yaml as a communication language between processes that are connected through sockets. When I open sockets, I use non blocking sockets. Thus when libyaml tries to read the file with fread, it returns an error. Indeed, as the non blocking flag is set, when there is nothing more to read, the fread call returns EWOULDBLOCK. As a hack, I have modified the yaml_file_read_handler function to return 1 if errno == EWOULDBLOCK and !ferror in the other cases... What do you think ? Thanks for your help Oscar |
|||
| #87 | fixed | front page example has broken delete for yaml_event_delete | xi | anonymous R |
| Description |
In the PARSER API Synopsis example program there is a memory bug. the while loop checks the type of the event.type but the event has already been deleted. the delete invalidates the event type under debian on my x86 system. to fix the bug, i had to introduce another integer variable to hold the type so that the loop can check that to know when to end. |
|||
