)]}'
{"oslo/vmware/image_transfer.py":[{"author":{"_account_id":8027,"name":"Vui Lam","email":"vui@vmware.com","username":"vui"},"change_message_id":"d0f179b2bf68e7667f753e0c63ed12bc0c222abc","unresolved":false,"context_lines":[{"line_number":81,"context_line":"    # as a file handle."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"    def seek(self, offset, whence\u003d0):"},{"line_number":84,"context_line":"        \"\"\"Set the file\u0027s current position at the offset."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"        This method throws IOError since seek cannot be supported for a pipe."},{"line_number":87,"context_line":"        \"\"\""}],"source_content_type":"text/x-python","patch_set":1,"id":"baada198_aec10550","line":84,"updated":"2014-07-24 06:37:08.000000000","message":"Yep, this makes more sense. The original fix was restricted to address the case that needed addressing then (when dealing with data whose size cannot be predetermined), but this class can\u0027t support random access in any meaningful way. As for why the code was no-op on seek and returning the max transfer size on tell, I can only postulate it might be to support use case of quckly determining the file-like\u0027s size with \n   f.seek(0,2)\n   size \u003d f.tell()\nThat\u0027s not a good justification for the code though.","commit_id":"9a9649fea812dc69213627cc3a9044e3cf8ff295"}]}